Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-87405

Display human-readable the rank on the card in the backlog.

XMLWordPrintable

    • 819
    • 8

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As a Product Owner, displayimg a human-readable rank (1, 2, 3, etc.) on the cards in the backlog would make prioritizing stories easier. This especially applies to larger backlogs.

      Use case:

      When we're ranking large numbers of new stories with the our customer in a planning meeting, we need to be able to quickly place these stories in the Top 20, Bottom 20, etc. Having a human readable number that reflected the stories position on the backlog would help with this. At present, we have to count these groupings by hand.

        1. column.png
          column.png
          45 kB

            [JRACLOUD-87405] Display human-readable the rank on the card in the backlog.

            Shmulik Hasson added a comment -

            Please add this capability

            Shmulik Hasson added a comment - Please add this capability

            Marcel Baumgrass added a comment -

            +1

            Hello, we need such a function.

            The ticket was created in 2017 and not solved yet in 2025. 

            Marcel Baumgrass added a comment - +1 Hello, we need such a function. The ticket was created in 2017 and not solved yet in 2025. 

            Tobias added a comment -

            +1

            Tobias added a comment - +1

            Mark Plumley added a comment -

            +1

            Mark Plumley added a comment - +1

            John Anson added a comment -

            +1!!

            John Anson added a comment - +1!!

            Kori Hartung added a comment - - edited

            We depend on rank when planning refinement sessions as well as in BRP when knowing how to move work around. The amount of work in miro done by scrum leads to add this info (that is often changing) is wild! This is a MUST NEED field. 

            Kori Hartung added a comment - - edited We depend on rank when planning refinement sessions as well as in BRP when knowing how to move work around. The amount of work in miro done by scrum leads to add this info (that is often changing) is wild! This is a MUST NEED field. 

            Mike Nguyen added a comment - - edited

            +1. Must have feature

            Mike Nguyen added a comment - - edited +1. Must have feature

            sseifried added a comment -

            +1 not seeing the rank as a numerical value is a real downer

            sseifried added a comment - +1 not seeing the rank as a numerical value is a real downer

            Jim Lenart added a comment -

            Our organization would find this request very valuable. Voted and watching.

            Jim Lenart added a comment - Our organization would find this request very valuable. Voted and watching.

            Elisabeth Stefanovic added a comment -

            +1

            Elisabeth Stefanovic added a comment - +1

              Unassigned Unassigned
              jburke@atlassian.com Justin Burke (Inactive)
              Votes:
              484 Vote for this issue
              Watchers:
              231 Start watching this issue

                Created:
                Updated: