• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core

      Starting from some Jenkins release in this year (cannot remember exactly, but seems that it first occured in winter/spring 2019), boolean parameters title started to display not left-hand side (as it was before), but right to boolean check mark. It looks not quite logical, so i doubt it's feature and not a bug. It affects both Freestyle and Pipeline projects.

          [JENKINS-59388] Broken formatting for Boolean parameters

          Igor Rondarev added a comment - - edited

          Related to JENKINS-56109 and JENKINS-55787

          Igor Rondarev added a comment - - edited Related to  JENKINS-56109 and  JENKINS-55787

          Daniel Beck added a comment -

          Daniel Beck added a comment - Caused by https://github.com/jenkinsci/jenkins/pull/3921

          Josh Soref added a comment -

          It's by design. It will look better when we switch away from the table layout.

          Josh Soref added a comment - It's by design. It will look better when we switch away from the table layout.

          Martin Jost added a comment -

          What is the plan to switch this layout ? And how is it supposed to look by then ?
          Currently the change looks very confusing in a list of different parameter types for a job.
          (Need to mentally jump between the different alignment for the parameters)

          Martin Jost added a comment - What is the plan to switch this layout ? And how is it supposed to look by then ? Currently the change looks very confusing in a list of different parameter types for a job. (Need to mentally jump between the different alignment for the parameters)

          There's an open PR that handles this: https://github.com/jenkinsci/jenkins/pull/3895.

          For context, labels above input elements and to the right of boolean elements is pretty standard. Bootstrap, which follows rather standards UI patterns, implements them like this: https://getbootstrap.com/docs/4.4/components/forms/#overview

          Félix Queiruga Balado added a comment - There's an open PR that handles this: https://github.com/jenkinsci/jenkins/pull/3895 . For context, labels above input elements and to the right of boolean elements is pretty standard. Bootstrap, which follows rather standards UI patterns, implements them like this: https://getbootstrap.com/docs/4.4/components/forms/#overview

          Sachin V added a comment -

          Any idea on when can this bug fix to make it to a Jenkins release ?

          Sachin V added a comment - Any idea on when can this bug fix to make it to a Jenkins release ?

          Tiran Meltser added a comment -

          Joining all the above with a request to fix this very disturbing issue...

          Tiran Meltser added a comment - Joining all the above with a request to fix this very disturbing issue...

          Mark Waite added a comment -

          tmeltser and others interested in a fix for this issue are encouraged to learn more about the transition from table formatting to div formatting in the Jenkins user interface. Please view the May 2020 Hackfest video for an overview of the types of improvements the conversion will provide. Please read the table to div migration page on jenkins.io. The Jenkins UX SIG would love to have additional help testing , adapting, and refining the transition.

          The question, "When will it be in a Jenkins release?" depends on help from Jenkins developers and Jenkins users.

          Mark Waite added a comment - tmeltser and others interested in a fix for this issue are encouraged to learn more about the transition from table formatting to div formatting in the Jenkins user interface. Please view the May 2020 Hackfest video for an overview of the types of improvements the conversion will provide. Please read the table to div migration page on jenkins.io. The Jenkins UX SIG would love to have additional help testing , adapting, and refining the transition. The question, "When will it be in a Jenkins release?" depends on help from Jenkins developers and Jenkins users.

            Unassigned Unassigned
            d_garry Igor Rondarev
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: