Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-7259

As a Rapid board user, paging feature on backlog should be implemented

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • 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.

      For some customer that has more than 300 issues in the backlog, it would be hard to deal with all the issues where you have to scroll down to no ends. It would be really great if we can configure the maximum of issues per page on the backlog or not to have the page at all. This would be a great improvement to the current Rapid board, as you might know, this paging feature has been introduced in Classic board yet it seems not being implemented in the new Rapid board. Certain customer uses this feature and expect this to be available in the new Rapid board as well.

      The page numbering should be put on top and bottom of the backlog for easier access of handling all the issues in the backlog. As an example, the following

        1. page1.PNG
          page1.PNG
          22 kB
        2. page2.PNG
          page2.PNG
          26 kB
        3. page3.PNG
          page3.PNG
          33 kB
        4. page4.PNG
          page4.PNG
          103 kB

            [JSWSERVER-7259] As a Rapid board user, paging feature on backlog should be implemented

            Daniel Borcherding added a comment -

            I just jumped over here from

            https://jira.atlassian.com/browse/GHS-7662

            I really don't think these two issues are related other than having the words "boards" and "pagination" in them.

            Can we get them at least moved to "relates to" so there is not confusion that GHS-7662 has been considered and rejected.

            Daniel Borcherding added a comment - I just jumped over here from https://jira.atlassian.com/browse/GHS-7662 I really don't think these two issues are related other than having the words "boards" and "pagination" in them. Can we get them at least moved to "relates to" so there is not confusion that GHS-7662 has been considered and rejected.

            Tom Kotecki (Inactive) added a comment -

            Many thanks for reporting this issue. We do not currently plan to add support for pagination on plan mode. Our thinking is that:

            • we made sure the new boards are performant with larger amounts of issues (even when dealing with say 1000 issues)
            • ...which is the size at which you most likely going to mostly look at issues on the top and maybe the bottom of the backlog. Should you need to reorder an issue from the middle to the top, bottom or add it into an upcoming sprint, you can do so easily by using a right-click context menu.
            • lastly, keeping all issues on a single screen allows you to quickly find any issue by using Ctrl-F/CMD-F browser shortcut.

            Kind regards

            Tom Kotecki
            Product Manager, JIRA Agile

            Tom Kotecki (Inactive) added a comment - Many thanks for reporting this issue. We do not currently plan to add support for pagination on plan mode. Our thinking is that: we made sure the new boards are performant with larger amounts of issues (even when dealing with say 1000 issues) ...which is the size at which you most likely going to mostly look at issues on the top and maybe the bottom of the backlog. Should you need to reorder an issue from the middle to the top, bottom or add it into an upcoming sprint, you can do so easily by using a right-click context menu. lastly, keeping all issues on a single screen allows you to quickly find any issue by using Ctrl-F/CMD-F browser shortcut. Kind regards Tom Kotecki Product Manager, JIRA Agile

            SYSGO GmbH added a comment -

            We have to maintain more than 300 issues. When doing that in the list, we get crazy because:

            • the menu bars scroll away and
            • ranking an issue to a higher place in an x-screen high page is undoable.

            It was much easier to hover in the classic planning board, get a list of issues on the other page and drop the issue where it belongs. The overview of the planning board is totally lost in the new boards (this is just one example of it).

            SYSGO GmbH added a comment - We have to maintain more than 300 issues. When doing that in the list, we get crazy because: the menu bars scroll away and ranking an issue to a higher place in an x-screen high page is undoable. It was much easier to hover in the classic planning board, get a list of issues on the other page and drop the issue where it belongs. The overview of the planning board is totally lost in the new boards (this is just one example of it).

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: