Why in the world would you configure the scrum style backlogs to include issues of all status's. The backlog is the BACKLOG and should not have items that are in progress or complete included. This makes backlog grooming and prioritization unnecessarily complex and arduous. I get that the strike though on the issue number is used to indicate the issue is done, but issues that are complete or in progress should not be cluttering the backlog. Applying a filter does not work, because filters apply to all views not just the display in the backlog.
Also. a more minor issue but still a nuisance, moving an issue that has a status of backlog from the backlog to a sprint as part of planning and refinement should automatically transition the issue to ready.
Is anyone else having these issues? And if so, have you found a simple solution? So far a script runner is the only solution we could find and that may or may not work. However, these are very basic Agile scrum concepts that should not require add-ons to enable.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
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