I have a project with a single closed sprint.
Several issues are assigned to this sprint and resolved, but have no assignee set.
These issues appear in the backlog for the project. I would expect that an issue that is resolved and in a sprint would not show up in the backlog, regardless of the values of other fields.
Can you explain this to me?
Wow, that makes absolutely no sense.
Issues do not show up in the backlog when they are in a sprint, until they are resolved. Then suddenly, they show up in the backlog.
Even worse, if they are unassigned, in a sprint, and show up in the backlog with any status.
I thought I understood this product, but I'm thoroughly confused at this point.
It can be confusing at first for sure!
If you think of the sprint as confined by the columns you have configured, it makes a little more sense. The issue won't complete the sprint until it reaches the final step. Although these are related to workflow steps, a sprint can just be a view into your workflow. If you have multiple teams working on an issue, it might make sense for it to be in the backlog on a QA board before the issue is closed, even though it was resolved in development.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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