-
Task
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.0-alpha-2
I installed Jenkins 2.0 alpha-2, and installed the recommended plugins, and noticed that there are a lot of UI fields that have no inline help.
Ideally, every single config field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct.
I will try to concentrate on the most popular plugins, as listed by Daniel's spreadsheet, and keep track of PRs from this ticket.
Though of course anyone who wants to help is welcome 
- is related to
-
-
- Open
-
-
-
- Closed
-
[JENKINS-33366] All UI fields in recommended plugins for Jenkins 2.0 should have English documentation
| Link | New: This issue is related to JENKINS-33364 [ JENKINS-33364 ] |
| Labels | Original: 2.0 | New: 2.0 user-experience |
| Description |
Original:
I installed Jenkins 2.0 alpha-2, and noted that — even with no plugins installed — there are a lot of UI fields that have no inline help. Some of it wasn't well written. Ideally, every single field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct. |
New:
I installed Jenkins 2.0 alpha-2, and installed the recommended plugins, and noticed that there are a lot of UI fields that have no inline help. Similarly, some plugins still refer to "slaves" rather than "agents" — prominently, this includes the "New item" text of the Pipeline plugin. Ideally, every single config field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct. I will try to concentrate on the most popular plugins, as listed by [Daniel's spreadsheet|https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit], and keep track of PRs from this ticket. Though of course anyone who wants to help is welcome :) |
| Description |
Original:
I installed Jenkins 2.0 alpha-2, and installed the recommended plugins, and noticed that there are a lot of UI fields that have no inline help. Similarly, some plugins still refer to "slaves" rather than "agents" — prominently, this includes the "New item" text of the Pipeline plugin. Ideally, every single config field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct. I will try to concentrate on the most popular plugins, as listed by [Daniel's spreadsheet|https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit], and keep track of PRs from this ticket. Though of course anyone who wants to help is welcome :) |
New:
I installed Jenkins 2.0 alpha-2, and installed the recommended plugins, and noticed that there are a lot of UI fields that have no inline help. Ideally, every single config field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct. I will try to concentrate on the most popular plugins, as listed by [Daniel's spreadsheet|https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit], and keep track of PRs from this ticket. Though of course anyone who wants to help is welcome :) |
| Link |
New:
This issue is related to |
| Labels | Original: 2.0 user-experience | New: 2.0 2.0-planned user-experience |
| Labels | Original: 2.0 2.0-planned user-experience | New: 2.0 user-experience |
| Workflow | Original: JNJira [ 169279 ] | New: JNJira + In-Review [ 183430 ] |
I'm thinking the probability of this happening for the initial 2.0 release is pretty low...