Is this intentional? Product Owners for teams using JIRA Agile are creating an aspirational release plan a number of sprints ahead, but before the next sprint is started, some of the issues will be removed as they total more than the team's velocity.
Then when reviewing the Sprint Report mid-sprint, those issues that are no longer in the current sprint backlog are still in the report under 'Issues Not Completetd', which creates an unusable report.
Unless it's a critical bug or blocker, voting is really the only way to impact getting them into a release. Non-critical issues are addressed based on a variety of considerations including how complex it is to fix, how many customers are affected, etc. One of the primary ways to measure impact is from the votes and customer feedback on the issue.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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