Why do issues assigned to a sprint, but with no assignee show up in the backlog

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?

1 answer

Can you check which workflow status is mapped to the Done column in your jira agile board. issues need to be in the done column for it to not appear in the backlog.


I have added a column for this project. Issues that are resolved are in the resolved column and issues that are closed are in the closed column.

Since the sprint is complete, all I can see is the report, and these issues show up correctly as resolved in the report.

Issues must be in the righmost cloumn for it to not appear in the backlog. Can you temporarily map the Resolved workflow status to the rightmost jiraagile column and see if that fixes your problem.


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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

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...

602 views 0 7
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you