|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loose translation of the short summary report's usability problems (all are classified minor), with additional comments in italics:
1. Inconsistent navigation
Recommendations:
2. Multiple links cannot be recognized as such
3. All tables (build history widget in the example) should have a 'Legend' link with explanation for the symbols used.
Maybe we could move the legend link to the footer?
4. Viewing files and raw console output (basically everything not using the regular basic layout) should not open in the same window.
5. Mandatory text fields are not recognizable as such except by their validation error.
Recommendation is to add an icon or other marking (such as an asterisk?) to mandatory form fields, and possibly some color highlighting.
6. Translation is incomplete
It's kind of ironic that the screenshot includes the 'help us' link from the Translation Assistance plugin. The specific issues highlighted are not in core, but an action and column from installed non-default plugins. Still, I've seen hardcoded strings in plugins that won't be translatable easily, and that must go.
7. Two buttons have the same functionality
I don't see the point of this, as with all other forms (consistency!) 'Save' leaves the form while 'Apply' does not. Users should be used to it from Windows.
8. View tabs that show global views (in My Views) are not recognizable as such before clicking them.
A horrible feature all around IMO
9. The inline description editor has no 'cancel' button.
This issue was much more vaguely described, but it boils down to the inline editor not having a cancel button