Usability Check Report

[Michael Rumpf]

Hi,

the company I work for has conducted a professional usability check of Jenkins.
How can we contribute the report results back to the community?

Regards,
      Michael

[Tom Fennelly]

Hi Michael.

Feel free to share your findings here. From that we can decide what JIRAs  need to be created etc.

Regards,

T.

[Michael Rumpf]

Hi Tom,

there is one issue, the report is completely in German.

The company is Deutsche Telekom where you need to go through an approval process (Usability, Accessibility) in order to provide a tool like Jenkins to internal projects.

What I have is a short report (Slides), a long report (Document) and a list of measures (Spreadsheet) that should be solved in order to allow disabled employees to access the tool.

I have attached the documents to this mail so that you can have a look. Google Translate is not ideal but should allow you to get an overview.

For documenting purposes, we need to show internally that we have at least reported the issues back to the "tool vendor", I would like to create a JIRA ticket in the Jenkins JIRA. To this ticket I would like to attach the documents and for each finding from the report we could create a sub-task or a separate task where each issue can be discussed.

Would that be OK?

Regards,

       Michael

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/c18HqJNAazg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f9fb118c-0f18-4d38-a5e9-2b031fa84474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ulli Hafner]

Hi Michael,

thanks for your detailed report! I think there are a lot of small issues in your report that would be easy to fix which would increase the usability of Jenkins. 

Currently we don’t use sub-tasks in Jira, so it would make sense to create new issues for each important item. We use labels (user-experience) to group similar issues. 

Ulli

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFu1rAswM216rbddtKDZ0bE1c4jwgUVfz4Piy8nbnzj09rBiaw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

<Kurzbericht_Software-Ergonomie_Jenkins_1.580.1.pdf><Masnahmenplan_Barrierefrei heit_Jenkins_v1.580.1.xlsx><Prüfbericht_Barrierefreiheit_Jenkins_v1.580.1.pdf>

[Tom Fennelly]

Hi Michael.

Sure, create a JIRA (https://issues.jenkins-ci.org/) of type "Improvement" against component "core" and attach the "user-experience" label to it (and of course attach your docs).

I tried translating the docs by viewing in google drive but that did not work so I need to try something else. In any case, I think any translation would need to be verified as being accurate.

Regards,

T.

[Michael Rumpf]

Hi,

I have created the following ticket:
https://issues.jenkins-ci.org/browse/JENKINS-26503

I have listed the 9 issues in the comments. Should I create a ticket per issue?

Regards,

      Michael

--

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/c18HqJNAazg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb9c6655-8f03-45f2-9460-ab47ced10f4f%40googlegroups.com.

[Ulli Hafner]

I think this is not required yet. If work on this issue is in progress we still can create new issues from the sub-tasks.  

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFu1rAteVEvQM7ZRQ4WWZ7xv2mzad6r85k0s2vFi04nMQ%3DvFYA%40mail.gmail.com.

[Daniel Beck]

Hi Michael,

thanks for sharing the report!

We have a few German speaking developers in the Jenkins project, so translating these as needed should not be a problem.

I think we should keep the one issue you wrote as the "PDF report issue" and create related issues as needed.

I added a longer translation/explanation of the usability issues from the summary report in a comment to the Jira issues. WRT to issue 2, I assume color is not a good enough indicator for a clickable link? And I don't understand issue 7 at all.

Overall, the short report paints a more positive picture of Jenkins usability than I'd have expected. Of course, the accessibility situation (blind users) is a lot worse, but I've only skimmed the second report.

Regards
Daniel

> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFu1rAteVEvQM7ZRQ4WWZ7xv2mzad6r85k0s2vFi04nMQ%3DvFYA%40mail.gmail.com.