This is my first community question.
Actually i created a workflow that refers to an Agile Scrum Board. I included some transistions in order to push back or 'ice' an already assigned ToDo with status ToDo. I created this status sequence for creation: "gray circle" into "backlog" into "ToDo".
THE PROBLEM: issues with status backlog do not appear in the Sprint/Backlog view. They are simply invisible for all sprints (since I cleared the sprint-field) and the sprint-backlog (since it does not show issues with a status diffrent to ToDo). So: I understand that issues with status=ToDo and an empty (!) sprint-field do appear in the overall backlog, but the status ToDo is already reserved for the "real" ToDos in the sprint after the Backlog-status in my workflow.
THE INTENDED solution: I would like to be able to map MORE than the ToDo-status (build-in) to the backlog outside the sprints. This feature is actually available for true Kanban projects with the special "Kanban backlog" column besides of the normal backlog column. Why cant I have such an elegant way in agile Scrum projects?
Any suggestion would be appreciated.
Deliver better and faster value to your customers with the Jira automation platform. Watch this Demo Den series below to learn how to use the new interface and set up automation rules to help your te...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events