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

Configuration page for pipelines has wrong focus

    Details

    • Similar Issues:

      Description

      Opening the configuration page, four sections are provided:

      • General
      • Build Triggers
      • Advanced Project Options
      • Pipeline

      Main work will very often and continuously be done in the last section namely the Pipeline section, particularly if a pipeline script is directly embedded. It would be more productive if this last section would be opened directly, and thus be in focus, so you can start or continue to edit the pipeline script.

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          CC gus reiber Tom FENNELLY FYI user feedback on the tabs.
          (But I still maintain scroll-tabs that remember scroll position is terrible UX.)

          Show
          danielbeck Daniel Beck added a comment - CC gus reiber Tom FENNELLY FYI user feedback on the tabs. (But I still maintain scroll-tabs that remember scroll position is terrible UX.)
          Hide
          michaelhuettermann Michael Hüttermann added a comment -

          Yes, it is 2.0-beta-1.

          Show
          michaelhuettermann Michael Hüttermann added a comment - Yes, it is 2.0-beta-1.
          Hide
          danielbeck Daniel Beck added a comment -

          and this is probably the most probably reason why you continuously re-open the config page, you have to always scroll down, or click the tab.

          We went through a few iterations on this. Earlier alpha releases didn't scroll, but actually split job configurations into tabs, i.e. you were only seeing a single section at a time. One of the behaviors implemented there was that your browser remembered which tab it was on last (per job type I think), and automatically selected that one. I.e. repeated config cycles as you describe had you start on the script section, and only see that one, unless you selected something else.

          Consensus later was that 'scroll tabs' are better, and with them, the automatic selection was extremely weird. I knew about this feature and still had no idea what was going on – the problem was, with everything on a single page, some sections may be so short that it's impossible to scroll down to them, etc.

          So implementing anything resembling what you're requesting would probably require switching from "scroll tabs" to actual tabs.

          Show
          danielbeck Daniel Beck added a comment - and this is probably the most probably reason why you continuously re-open the config page, you have to always scroll down, or click the tab. We went through a few iterations on this. Earlier alpha releases didn't scroll, but actually split job configurations into tabs, i.e. you were only seeing a single section at a time. One of the behaviors implemented there was that your browser remembered which tab it was on last (per job type I think), and automatically selected that one. I.e. repeated config cycles as you describe had you start on the script section, and only see that one, unless you selected something else. Consensus later was that 'scroll tabs' are better, and with them, the automatic selection was extremely weird. I knew about this feature and still had no idea what was going on – the problem was, with everything on a single page, some sections may be so short that it's impossible to scroll down to them, etc. So implementing anything resembling what you're requesting would probably require switching from "scroll tabs" to actual tabs.
          Hide
          tfennelly Tom FENNELLY added a comment -

          Michael Hüttermann and Daniel Beck

          With the tabs option (Michael Hüttermann see Daniel's comment above), the activated section (on opening a config) would be the last active section "for that job" i.e. not per job type.

          So, if you were working on pipeline config "A", and the last time you were working that config you were editing the pipeline script, then the next time you opened pipeline config "A", the pipeline script section would be the section that would be activated initially (i.e. you'd see first i.e. no need to select it).

          Show
          tfennelly Tom FENNELLY added a comment - Michael Hüttermann and Daniel Beck With the tabs option ( Michael Hüttermann see Daniel's comment above), the activated section (on opening a config) would be the last active section "for that job" i.e. not per job type. So, if you were working on pipeline config "A", and the last time you were working that config you were editing the pipeline script, then the next time you opened pipeline config "A", the pipeline script section would be the section that would be activated initially (i.e. you'd see first i.e. no need to select it).
          Hide
          michaelhuettermann Michael Hüttermann added a comment -

          Thanks for the feedback. Sounds fine.
          Any solution would probably work which prevents the user being forced to actively and continuously navigate to the script section since this one is the section most of us will work on continuously, whereas the other parts, particullarly the ones on top, will be more stable, without many changes, during the continuous work on the pipeline.

          Show
          michaelhuettermann Michael Hüttermann added a comment - Thanks for the feedback. Sounds fine. Any solution would probably work which prevents the user being forced to actively and continuously navigate to the script section since this one is the section most of us will work on continuously, whereas the other parts, particullarly the ones on top, will be more stable, without many changes, during the continuous work on the pipeline.

            People

            • Assignee:
              jglick Jesse Glick
              Reporter:
              michaelhuettermann Michael Hüttermann
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: