Ability to quickly rank stories in Scrum backlog based on rank of epics

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Won't Fix
    • None
    • Component/s: None
    • None

      As a Product Owner

      I want to quickly rank stories in the Scrum Backlog when I rank their parent Epic

      So that I can quickly tidy up a board that may have been shuffled by various people creating new stories against epics but not ranking them


      Currently you can do 2 things in a Scrum board:

      • Rank stories against one another in the main part of the backlog
      • Rank epics against one another in the Epics side-bar

      This is fine and I understand the value of keeping these rankings separate but most of the time what happens is as follows:

      1. The PO creates an epic and ranks it against others
      2. The Development team splits this epic in many child stories over time. When this happens for several epics, with epic-less defects created as well in the meantime, the all the stories for one epic are scattered in the board 
      3. Regularly, prior to the PBR, the Product Owner wants to make sure the ranking of the stories represent the ranking of the epics.

      I am sure there are various ways to implement this functionality but as a possible option, there could be a button/toggle in the Epics side-bar. When ticked, if an epic is ranked on top of another epic then it also ranks all the stories for the epic ahead of the highest ranked story on the other epic.

      Another solution would be to add a new contextual menu against epics in the side-bar (with Edit Name, Mark as Done, etc...) called "Rank stories together", which would rank all stories on the epic after the highest ranked story in this epic. That would be enough to prevent the cumbersome selection and dragging of stories.

       

              Assignee:
              Unassigned
              Reporter:
              Johann Moro
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: