• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      As a user, I would like to be able to Favorite boards. I envision this behavior being similar to favoriting Dashboards in JIRA.

          Form Name

            [JSWSERVER-9346] As a user, I would like to be able to Favorite boards

            Is there any feedback on being able to improve the usability of the boards. We now have hundreds of boards and 1) you cannot sort or filter the list 2) you cannot set favorites. I am literally using F5 to try and search the page for the board that I need.

            Why do we have hundreds of boards? Because, we have 40 JIRA projects, with departments other than scrum teams using them to manage work. Whether it is for specific customer implementations, special projects, release management, quality record/ISO CAPA management, etc...there are LOTS. Every scrum team also has at least 2 if not 3. Why? Because kanbans don't have plan mode with epics and versions so scrum board is created for strictly planning purposes and the kanban for mgmt of the actual team work; a kanban is also often used for managing the priorities of getting stories to be in a ready for grooming state. When a dozen development teams...that yields almost 40 boards alone.

            PLEASE, can we have some updates in terms of improving the usability and access of these boards.

            Karie Kelly added a comment - Is there any feedback on being able to improve the usability of the boards. We now have hundreds of boards and 1) you cannot sort or filter the list 2) you cannot set favorites. I am literally using F5 to try and search the page for the board that I need. Why do we have hundreds of boards? Because, we have 40 JIRA projects, with departments other than scrum teams using them to manage work. Whether it is for specific customer implementations, special projects, release management, quality record/ISO CAPA management, etc...there are LOTS. Every scrum team also has at least 2 if not 3. Why? Because kanbans don't have plan mode with epics and versions so scrum board is created for strictly planning purposes and the kanban for mgmt of the actual team work; a kanban is also often used for managing the priorities of getting stories to be in a ready for grooming state. When a dozen development teams...that yields almost 40 boards alone. PLEASE, can we have some updates in terms of improving the usability and access of these boards.

              Unassigned Unassigned
              bberenberg Boris Berenberg (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: