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

As a Product Owner, I want new PBIs quarantined from the Backlog until I rank them

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • 4
    • 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.

      An issue we are facing is that the Product Owner has trouble identifying new items that need ranking, and as such they they get lost in the middle of the backlog. Especially when they are created whilst the Planning Board is open.

      As a workaround...
      I am using colour and status to indicate an item has not yet been ranked.
      This way all 'new' items show up. However this requires the Product Owner to transition these items/issues after they haver been ranked, which is clumsy.

      On our physical wall, we have a separate section where all new cards are posted until they are ranked.
      It has a green heading called "New Items".
      When the Product Owner reviews the backlog, any "New Items" are ranked.

      What I would like to see is a similar tool avalible in Jira.
      e.g. a separate section of the Planning Board, where new items are quaranteened, until physically dragged into a position in the backlog.

      I could see this being implemented by not auto-assigning issues a rank.

      For backwards compatiility I see this as a configurable feature, so as not to shock product owners on upgrade.

        1. Mockup.png
          Mockup.png
          100 kB
        2. screenshot-1.png
          84 kB

          Form Name

            [JSWSERVER-11139] As a Product Owner, I want new PBIs quarantined from the Backlog until I rank them

            Alexey Larchenko added a comment -

            Workaround for simplified projects which works really well for us:

            • Create a fake sprint and call it e.g. Triage
            • Ask everyone to add new issues there
            • When they are triaged, they can be moved to backlog or sprints directly
            • You can add other fake sprints and organize your workflow Triage -> Grooming

            Alexey Larchenko added a comment - Workaround for simplified projects which works really well for us: Create a fake sprint and call it e.g. Triage Ask everyone to add new issues there When they are triaged, they can be moved to backlog or sprints directly You can add other fake sprints and organize your workflow Triage -> Grooming

            Jo Astley added a comment - - edited

            +1 this should be configurable to appear at the top or the bottom. The problem I have with this appearing at the top (Which is currently seems to do) is that my backlog is in priority order and therefore incorrect tickets could be selected from the top which is in fact just a newly created ticket... 

            Jo Astley added a comment - - edited +1 this should be configurable to appear at the top or the bottom. The problem I have with this appearing at the top (Which is currently seems to do) is that my backlog is in priority order and therefore incorrect tickets could be selected from the top which is in fact just a newly created ticket... 

            C Gibson added a comment -

            +1

             

            Or at least JSWSERVER-5368

            C Gibson added a comment - +1   Or at least JSWSERVER-5368

            Dave F added a comment -

            +1, possibly in conjunction or as a 4th option for this request. https://jira.atlassian.com/browse/JSWSERVER-5368

            Dave F added a comment - +1, possibly in conjunction or as a 4th option for this request.  https://jira.atlassian.com/browse/JSWSERVER-5368

            Pierre ALLYNDREE added a comment -

            +1 I do that all the time and is pretty annoying to move stories from bottom to top of backlog !!

            Pierre ALLYNDREE added a comment - +1 I do that all the time and is pretty annoying to move stories from bottom to top of backlog !!

            Alfredzo Nash added a comment - - edited

            +1000 New issues should definitely default to the top of the backlog. As a Scrum master attempting to influence AGILE/DevOps practices within my organization, this feature allows for faster review of PBI while offsetting slower planning nuisances during Sprint planning.  

            Alfredzo Nash added a comment - - edited +1000 New issues should definitely default to the top of the backlog. As a Scrum master attempting to influence AGILE/DevOps practices within my organization, this feature allows for faster review of PBI while offsetting slower planning nuisances during Sprint planning.  

            Steve Pritchard added a comment -

            I'm finding I want issues at the top so that we can review them. I can always "Send to bottom" if we decide they are low priority.

            Agree with others that this should be configurable (e.g. Configure Board - Kanban, or project-level).

            Steve Pritchard added a comment - I'm finding I want issues at the top so that we can review them. I can always "Send to bottom" if we decide they are low priority. Agree with others that this should be configurable (e.g. Configure Board - Kanban, or project-level).

            Daniel Howard added a comment -

            +1

            Daniel Howard added a comment - +1

            Adam Archer added a comment -

            I find I'm constantly scrolling to the bottom or changing filters to get to the create button, a create button up higher would be great, the top button could add to the top of the backlog, the bottom one to the bottom

            Adam Archer added a comment - I find I'm constantly scrolling to the bottom or changing filters to get to the create button, a create button up higher would be great, the top button could add to the top of the backlog, the bottom one to the bottom

            Chris Kelly added a comment -

            +1

            Chris Kelly added a comment - +1

              Unassigned Unassigned
              4f1255b607ed James Rickards
              Votes:
              82 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated: