-
Task
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.0-alpha-2
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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct.
These are the areas, in order of importance I'd like to initially look at:
- Freestyle Job Config
- Manage Jenkins
- Configure System
- Agent configuration
- Configure Global Security
- New Item page (perhaps)
As each item alone can be fairly large, and time-consuming, I'm going to submit them as separate PRs.
- is related to
-
JENKINS-33366 All UI fields in recommended plugins for Jenkins 2.0 should have English documentation
-
- Open
-
- links to
[JENKINS-33364] All UI fields in core Jenkins should have English documentation
Link | New: This issue is related to JENKINS-33366 [ JENKINS-33366 ] |
Labels | Original: 2.0 | New: 2.0 user-experience |
Remote Link | New: This issue links to "PR #2101 (Web Link)" [ 14050 ] |
Labels | Original: 2.0 user-experience | New: 2.0 2.0-planned user-experience |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
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 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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct. |
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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct. |
New:
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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct. From PR 2101, these are the areas, in order of importance I'd like to initially look at: * Freestyle Job Config * Manage Jenkins * Configure System * Agent configuration * Configure Global Security * New Item page (perhaps) As each item alone can be fairly large, and time-consuming, I'm going to submit them as separate PRs. |
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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct. From PR 2101, these are the areas, in order of importance I'd like to initially look at: * Freestyle Job Config * Manage Jenkins * Configure System * Agent configuration * Configure Global Security * New Item page (perhaps) As each item alone can be fairly large, and time-consuming, I'm going to submit them as separate PRs. |
New:
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 have inline help in English (as a start), and the help text should be unambiguous, and grammatically correct. These are the areas, in order of importance I'd like to initially look at: * Freestyle Job Config * Manage Jenkins * Configure System * Agent configuration * Configure Global Security * New Item page (perhaps) As each item alone can be fairly large, and time-consuming, I'm going to submit them as separate PRs. |
Epic Link |
New:
|
Epic Link |
Original:
|