The backlog tab displays the workspace backlog, planned or those sprints being planned, and the active sprint.
This can be confusing to users because the backlog page leads one to believe that all isssues on the page are in fact, backlog.
However, the active sprint detail displays the "done" issues for that sprint, which are not technically, backlog. It clouds the view of what the backlog actually is when including "done" items.
In our case, it is confusing users, especially when introducing new users to the concept of backlog, and trying to explain "done" issues are not backlog, but the supporting filtering and page naming shows otherwise.
If you have experienced some of the same issues, please vote on the feature request supporting making a change in this area so it is more clear to users.
JSWCLOUD-26416 Rename or rework the Backlog to avoid confusion
I guess it depends on your point of view but, when it comes to the active sprint, I would want to see any Done items in the active sprint section of the backlog. That way I have an accurate view of what has been accomplished in the sprint and it can also help with sprint review as sometimes it's easier to see a longer list of issues in the backlog view than on the active sprint view.
If you're seeing these Done items in future sprints as well or the Backlog section, that would be an indicator that the Done status is not mapped to the right-most column on the board, as Jira only considers work items to be completed in a sprint if they are in a status that is mapped to the right-most column.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.