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

Developer can see all top level folders as a grouping on the dashboard

    • Icon: Story Story
    • Resolution: Postponed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • frank, tethys, christmas, pannonian, 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2

      User can see all pipelines for an organization grouped on the dashboard.

      In Scope

      • For regular folders
      • For Organization folders
        • Organization avatar is displayed in the grouping
        • If no avatar available then use the regular folder avatar
      • Dashboard remains alphabetically sorted
      • Check that we have consistent hover states (e.g. it highlights as you hover)

      Notes
      This story originally had all non-org folders grouped as "other". We no longer want to do this and that part of the provided mockups can be ignored.

          [JENKINS-40209] Developer can see all top level folders as a grouping on the dashboard

          Brody Maclean added a comment -

          Brody Maclean added a comment - https://zpl.io/Z1yMpNa

          James Dumay added a comment -

          cliffmeyers if you do get stuck for work this one can be brought into the sprint at any time.

          James Dumay added a comment - cliffmeyers if you do get stuck for work this one can be brought into the sprint at any time.

          Michael Neale added a comment -

          It is not clear to me if we have the api metadata to know if a top level older is a github org, but I am sure can be added if not.

          Perhaps a starting point is to group to level folders like this always. The design shows a grouping of things with some nested folders - this to me implies all top level folders should be shown like this.
          IF we know a top level folder is a github org, we can decorate it as such.

          Woudl this make sense ?

          Michael Neale added a comment - It is not clear to me if we have the api metadata to know if a top level older is a github org, but I am sure can be added if not. Perhaps a starting point is to group to level folders like this always. The design shows a grouping of things with some nested folders - this to me implies all top level folders should be shown like this. IF we know a top level folder is a github org, we can decorate it as such. Woudl this make sense ?

          Cliff Meyers added a comment -

          Yeah, absolutely, we just need to decide how that other metadata should be decorated - hopefully the perf impact would be minimal.

          Cliff Meyers added a comment - Yeah, absolutely, we just need to decide how that other metadata should be decorated - hopefully the perf impact would be minimal.

          James Dumay added a comment -

          James Dumay added a comment - cliffmeyers would this do? https://github.com/jenkinsci/blueocean-plugin/pull/661

          Michael Neale added a comment -

          yes something like what james suggested - but I think starting with top level (only) folder grouping as per design is a great start and would make a bunch of people happy.

          Michael Neale added a comment - yes something like what james suggested - but I think starting with top level (only) folder grouping as per design is a great start and would make a bunch of people happy.

          James Dumay added a comment -

          We are no longer supporting organisation folders.

          James Dumay added a comment - We are no longer supporting organisation folders.

            sophistifunk Josh McDonald
            jamesdumay James Dumay
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: