Backlog Organization

[Jenny Luker]

Our Product Team is looking for a way to further organize the backlog into statuses and move them accordingly.

We'd like a view separate from the scrum board that houses backlog cases that aren't quite ready to be added to a sprint.

Backlog > Requirements in Progress > Ready for Tech Review > Ready for Refinement

The only way we can think to accomplish this is to create fake sprints for each of these categories and move the cases through them without ever starting the sprints.  

Anyone have any suggestions or handled something similar?

[Trudy Claspill]

If you are working with a Company Managed project:

Another alternative is to have all the unreviewed items start in a different project. You can have a workflow there that represents the different statuses of the review project. When they reach the last status where they have been fully reviewed and are ready for the team backlog, you could use Automation to automatically "move" them to the project used by your scrum board.

Or, you can add the review statuses to the beginning of your workflow in the original project, and change your board filter so that it doesn't include the issues in those statuses except for the ones in the last, "fully reviewed/ready for assigning to sprints" status.

[Pramodh M]

@Jennifer Luker 

Yep if you really need to use the separate backlogs, that's about it.

But you'll be missing out on what Jira offers

Or create the columns in Jira board and map them to respective stats

Let me know if you have any queries