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

Better config page navigation - phase 2 (and beyond)

XMLWordPrintable

      Another iteration of UX improvements to the config pages following on from JENKINS-32357.

      Possible target features for "phase 2" (and beyond)

      1. More JavaScript unit tests. In particular around the finder feature.
      2. Split out config/table-metadata.js. Refactor config/table-metadata.js to extract ConfigTableMetaData, ConfigSection and ConfigRowSet into modules of their own. They've outgrown where they are.
      3. Better row-set modeling in the JavaScript API. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
      4. Section merging. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
      5. Section extraction. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
      6. Finder auto-complete.
      7. Try accordion based navigation (instead of Tabs). See config/tabbar.js and do something similar for accordions.
      8. Try a "left tree" based navigation (instead of Tabs). See config/tabbar.js and do something similar etc.
      9. New Item Wizards. Maybe we can create some "New Item" wizards that help users configure new Jobs more easily. E.g. for a freestyle job, something that guides you to configure the SCM and then some Build actions. I think this would be especially useful for new Jenkins users. Of course it needs to be something that can be turned off easily (with a "don't show me this anymore" type checkbox).

      What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.

          [JENKINS-32578] Better config page navigation - phase 2 (and beyond)

          Tom FENNELLY created issue -
          Tom FENNELLY made changes -
          Link New: This issue depends on JENKINS-32357 [ JENKINS-32357 ]
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357]. New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          #
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          #
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was create by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was create by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).
          Tom FENNELLY made changes -
          Summary Original: Better config page navigation - phase 2 New: Better config page navigation - phase 2 (and beyond)
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordions based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs).
          # *Try a "left tree" based navigation* (instead of Tabs).

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs). [See config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.
          # *Try a "left tree" based navigation* (instead of Tabs). [See config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc.

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs). [See config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.
          # *Try a "left tree" based navigation* (instead of Tabs). [See config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc.

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.
          # *Try a "left tree" based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc.

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.
          Tom FENNELLY made changes -
          Description Original: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.
          # *Try a "left tree" based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc.

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.           		New: Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].

          h2. Possible target features for "phase 2" (and beyond)
          # *More JavaScript unit tests*. In particular around the finder feature.
          # *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.
          # *Better {{row-set}} modeling in the JavaScript API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.
          # *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.
          # *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.
          # *Finder auto-complete*.
          # *Try accordion based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.
          # *Try a "left tree" based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc.
          # *New Item Wizards*. Maybe we can create some "New Item" wizards that help users configure new Jobs more easily. E.g. for a freestyle job, something that guides you to configure the SCM and then some Build actions. I think this would be especially useful for new Jenkins users. Of course it needs to be something that can be turned off easily (with a "don't show me this anymore" type checkbox).

          What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.

            tfennelly Tom FENNELLY
            tfennelly Tom FENNELLY
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: