Many of our projects have huge backlogs with more than 100 issues. It gets very difficult to see and prioritize these when Sprint planning.
We've tried a workaround by creating a sprint (we have parallel sprints enabled), "Top Backlog" but it's not an ideal solution - the "sprint" was accidentally closed and all the issues went into the backlog.
It would be great to have two real, separate Backlogs that we could re-title so as to separate out issues.
Another option is to have 2 different statuses in the workflow, one for Open tickets and another for those tickets that are qualified to appear in the backlog (maybe call it 'reviewed' or 'ready for planning' or something similar). You can then make sure only the qualified tickets (in the second state) appear in your actual backlog.
You can move tickets from the first state to the second state using a Kanban board if you like the drag and drop - more like a backlog planning
Currently there isn't one specific feature to create different backlogs in one Agile board, but one workaround I can think of at this point would be to do something similar to:
The good part of this implementation is that you can create as many backlogs as you want, since they are based on labels.
We hope this helps as a workaround!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs