Details
-
Epic
-
Status: In Progress (View Workflow)
-
Minor
-
Resolution: Unresolved
-
-
Jenkins 2.179
Description
This is the preferred style:
As opposed to:
or
–
I'm going to point to this issue for a bunch of plugins.
Note: my initial efforts relied on using optionalBlock instead of entry + checkbox. Unfortunately this interacts poorly w/ the form submission magic, and so rather than continue down that path, I'm switching to moving label's from the entry to the checkbox. The rendering won't generally change from the examples above.
Please don't close this ticket when an individual PR is merged, I'm using the same ticket for many plugins.
Attachments
Issue Links
- is related to
-
JENKINS-61870 Git plugin UI transition for shallow clone needs more changes
-
- Closed
-
- relates to
-
JENKINS-62437 Change Jenkins configuration UI from tables to divs
-
- In Progress
-
-
JENKINS-56109 Jenkins Core: Change Jenkins configuration UI from tables to divs
-
- Closed
-
- links to
Josh, i'm terrbily sorry, but don't you think that this decision is a bit premature? I agree with Adrien that currently all job parameters looks like a table that's easy to watch and use, and 'jumping' to the right side at boolean parameters is, to be honest, not very easy to read (also from the same UX point of view, we get empty gap at the left side where label originally was; i've even created a bug report (JENKINS-59388) and have rewritten several jobs in our organization from 'booleanParam' to 'choice' with 'true'/'false' values before i found this ticket). Probably it would be better to make it configurable or add another type (e.g. BooleanLabel) with UI you propose.