Repository navigation
[JENKINS-55787] Switch labels from entry to checkbox #665
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.
Originally reported by jsoref, imported from: Switch labels from entry to checkbox
- assignee: jsoref
- status: In Progress
- priority: Minor
- component(s): bitbucket-branch-source-plugin, datadog-plugin, github-plugin, jclouds-plugin, jobconfighistory-plugin, mailer-plugin, mercurial-plugin, qc-plugin, slack-plugin, ssh-slaves-plugin, tap-plugin, wix-plugin, workflow-cps-global-lib-plugin
- label(s): pipeline-model-definition-plugin, xunit
- resolution: Unresolved
- votes: 0
- watchers: 9
- imported: 2025-12-08
Raw content of original issue
This is the preferred style:
–
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.
Activity
jenkins-infra-bot commentedon Jan 25, 2019
Remote links associated with this issue:
jenkins-infra-bot commentedon Feb 14, 2019
Raw content of original comment:
Sorry jsoref! I am so used to add the link to the release notes in the Wiki, move to released, and close... then after a few minutes I realized it was not a tap-plugin issue, nor assigned to me.
I apologize. Re-opened.
jenkins-infra-bot commentedon Feb 14, 2019
jsoref:
Raw content of original comment:
I'm not used to using this JIRA either.
Since this JIRA allows selecting multiple components, it made sense to use a single ticket for all the instances, so I'm trying to take advantage of that feature.
jenkins-infra-bot commentedon Mar 29, 2019
Raw content of original comment:
Thank you jsoref! I'm speaking about mailer-plugin, as you filled a PR on this plugin. I've attached the screenshots in the PR you opened to see the diff.
Even if I agree with you that we should have the checkbox before the label, the fact that all Jenkins configurations are structured like a table (with the left column the label and the right column for the field), I fear that changing this might cause some incomprehension.
jenkins-infra-bot commentedon Mar 29, 2019
jsoref:
Raw content of original comment:
alecharp: once this change is mostly done, JENKINS-56109">
JENKINS-56109/ jenkinsci/jenkins#3895 will change the layout away from tables. Note: I'm currently taking a short hiatus from jenkins.jenkins-infra-bot commentedon Sep 4, 2019
Raw content of original comment:
Why is the state of this ticked resolved(fixed) ?
IMO, it should be set to resolved, once all plugins have the PRs merged, and for the jclouds-plugin, I can say the PR is incomplete: You missed 10 more checkboxes. Therefore; not (yet) merged!
jenkins-infra-bot commentedon Sep 6, 2019
Raw content of original comment:
jenkinsci/jclouds-plugin#132 has been merged.
jenkins-infra-bot commentedon Sep 19, 2019
Raw content of original comment:
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">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.
jenkins-infra-bot commentedon Sep 19, 2019
Raw content of original comment:
I've also read JENKINS-56109">
JENKINS-56109story and in common i agree that these 'name'/'value' tables look a bit old-fashioned, and a gap between label and checkbox isn't good too (especially when it's large), but now we've got 'mix' of styles.jenkins-infra-bot commentedon Jan 10, 2020
gzussa:
Raw content of original comment:
Regarding the Datadog Plugin, we should be good with our latest release 1.0.0. Let us know if this is not the case.
- https://github.com/jenkinsci/datadog-plugin/blob/master/src/main/resources/org/datadog/jenkins/plugins/datadog/DatadogGlobalConfiguration/config.jelly#L77-L81
- https://github.com/jenkinsci/datadog-plugin/blob/master/src/main/resources/org/datadog/jenkins/plugins/datadog/DatadogJobProperty/config.jelly#L19
jenkins-infra-bot commentedon Feb 18, 2020
basil:
Raw content of original comment:
FYI, the changes to the Timestamper plugin have been merged in jenkinsci/timestamper-plugin#32 and released in Timestamper 1.11.
jenkins-infra-bot commentedon Jun 19, 2020
Raw content of original comment:
Changes to the git plugin have been released as Git plugin 4.3.0 - June 19, 2020
jenkins-infra-bot commentedon Feb 9, 2025
Raw content of original comment:
5 years later. Can this be closed now?
1 remaining item
jenkins-infra-bot commentedon Dec 8, 2025
[Original
relates_tofrom Jira: JENKINS-61870]