Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67198

Jenkins 2.320 Job configuration dialog width too small

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • 2.331

      The new job configuration dialog (introduced by PR #5842 width is too small. On a 27'' Monitor it just fills 1/4 of the screen. Additionally, the tab navigation (and the background) is using 1/2 of the screen which looks somewhat strange. It makes sense to restore the old size in order to reduce the scrolling amount required to see all details.

          [JENKINS-67198] Jenkins 2.320 Job configuration dialog width too small

          Ulli Hafner added a comment -

          Seems that in the new screenshot the forms still do not use the whole area of the tabs container? There is still empty gray area on the right. 

          Ulli Hafner added a comment - Seems that in the new screenshot the forms still do not use the whole area of the tabs container? There is still empty gray area on the right. 

          Igor Hx added a comment - - edited

          Please fix this, because of this we're stuck at 2.317, as this is a showstopper.

           

          Igor Hx added a comment - - edited Please fix this, because of this we're stuck at 2.317, as this is a showstopper.  

          Ian Williams added a comment -

          igorhx, how exactly is this a "showstopper"? It would seem to be that this is more of a minor UI annoyance. It does not appear to impede the input/modification of field data.

          While I respect drulli 's original classification and danielbeck 's reclassification, were I creating this issue, based on the Jenkins classification, I would have classified this as a "Minor" issue at best (at worst?).

          I also think the Field should be relabelled more appropriately as "Severity", given Jenkins own guidance,

          This is not how urgently you want it fixed.

          as that seems to more correctly reflect its intended and common use.

          Ian Williams added a comment - igorhx , how exactly is this a "showstopper"? It would seem to be that this is more of a minor UI annoyance. It does not appear to impede the input/modification of field data. While I respect drulli 's original classification and danielbeck 's reclassification, were I creating this issue , based on the Jenkins classification , I would have classified this as a "Minor" issue at best (at worst?). I also think the Field should be relabelled more appropriately as "Severity", given Jenkins own guidance, This is not how urgently you want it fixed. as that seems to more correctly reflect its intended and common use.

          Max de Graaf added a comment -

          We are running the version with this particular problem. We can't revert to an older version because of dependencies on plugins so we are stuck. If this should be classified as minor or critical I don't know. What i do know is the simple fact that we using the "|Execute shell Command" section a lot with a lots of scripting in there. Now with this annoying problem we copy the script into another editor, make the required changes and copy it back in the Jenkins UI. So i would not call it a showstopper, but for us its not a minor issue for sure.

          Max de Graaf added a comment - We are running the version with this particular problem. We can't revert to an older version because of dependencies on plugins so we are stuck. If this should be classified as minor or critical I don't know. What i do know is the simple fact that we using the "|Execute shell Command" section a lot with a lots of scripting in there. Now with this annoying problem we copy the script into another editor, make the required changes and copy it back in the Jenkins UI. So i would not call it a showstopper, but for us its not a minor issue for sure.

          Ian Williams added a comment -

          I'm just suggesting it's "Minor loss of function, or other problem where easy workaround is present." There appears to be no loss of functionality; horizontal scrolling or copy/pasting to an external editor is a trivial workaround, making it an "annoying problem", as you note.

          Reference: IEEE Std 1044-2009: IEEE Standard Classification for Software Anomalies - Annex A

          Ian Williams added a comment - I'm just suggesting it's "Minor loss of function, or other problem where easy workaround is present." There appears to be no loss of functionality; horizontal scrolling or copy/pasting to an external editor is a trivial workaround, making it an "annoying problem", as you note. Reference: IEEE Std 1044-2009: IEEE Standard Classification for Software Anomalies - Annex A

          Max de Graaf added a comment -

          I agree with you Ian. But keep in mind this particular problem has been reported as fixed several times already in previous versions.

          Max de Graaf added a comment - I agree with you Ian. But keep in mind this particular problem has been reported as fixed several times already in previous versions.

          Igor Hx added a comment -

          I understand you guys, but from our customer point of view this is a serious issue - something what worked suddenly stopped working weeks ago and the fix is being postponed.

          Copying the contents to an external editor and then copying back it's indeed a workaround, but it's annoying.

          So we will stick with latest working version 2.317 and hopefully get a fix in near future...

          Have a nice holiday!

          Igor Hx added a comment - I understand you guys, but from our customer point of view this is a serious issue - something what worked suddenly stopped working weeks ago and the fix is being postponed. Copying the contents to an external editor and then copying back it's indeed a workaround, but it's annoying. So we will stick with latest working version 2.317 and hopefully get a fix in near future... Have a nice holiday!

          Daniel Beck added a comment -

          2.317

          In that case you should probably install https://plugins.jenkins.io/remoting-security-workaround/ unless you fully trust all code you're building.

          Daniel Beck added a comment - 2.317 In that case you should probably install https://plugins.jenkins.io/remoting-security-workaround/ unless you fully trust all code you're building.

          Ulli Hafner added a comment - - edited

          timja: From my understanding PR#5923 did not fix the problem yet. In my review the sizes of the dialog and the tab did not match yet. 

          Ulli Hafner added a comment - - edited timja : From my understanding PR#5923 did not fix the problem yet. In my review  the sizes of the dialog and the tab did not match yet. 

          Tim Jacomb added a comment -

          It makes it a lot better, (I added that in the links to).

          (The Jira ticket status here doesn't really make a lot of sense, it will be done in multiple pull requests with the main fix coming soon)

          Tim Jacomb added a comment - It makes it a lot better, (I added that in the links to). (The Jira ticket status here doesn't really make a lot of sense, it will be done in multiple pull requests with the main fix coming soon)

            janfaracik Jan Faracik
            drulli Ulli Hafner
            Votes:
            9 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: