Completed sprint stories still appear in backlog (possible bug)

So I just completed my sprint and it said I had 0 incomplete issues on my Active Sprints page. When I completed the sprint, the sprint was removed from the Agile Board view, but all the Story Issue Types were moved to the backlog rather than being removed. Each story status is in the final stage of the workflow, "Production". Production is definitely marked as a final stage in the Story issue type workflow (it's green on the workflow view). 

Here's where it starts to get strange, and almost seems like I found a bug of some type. All these stories' Sprint fields are populated with 17.11 (name of completed sprint), and the query for the backlog issues is "project = SE and sprint is empty ORDER BY Rank ASC". So it should only show issues that have an empty sprint field. When I click the "view in issue navigator" button to the right of the Backlog title on the Agile board, a new page is loaded with the same query used for the backlog (but it's in the issue navigator screen). The list resulting from that query shows none of the issues showing in the backlog from the completed sprint I mentioned.

So I'm just trying to figure out why these stories from the sprint I just completed were moved to my project's backlog? How it's possible for them to be there when they have populated sprint fields, and the query says that the sprint has to be empty. Also, why would these stories not show up in the issue navigator when i use the exact same query used for the backlog on the Agile Board view?

1 answer

0 votes

To see what is happening here, simplify.

Jira has an annoyingly inconsistent approach to "something is done", but despite that, it is often easy to define when you know where to look.

When you look at a Scrum board, it is simple.  The issues in the far right hand column are "done", and the rest are not.

The "green" or "final stage of the workflow" is irrelevant to the Scrum board.  All that matters is "issue in last column".  If it's not in the last column when you end the sprint, it's not done, so it moves to the next sprint or backlog.

Fixed. It did have to do with the To Do and Done. Was harder to do once it was removed from the active sprint. Thanks!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,719 views 17 21
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