Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Closed issues showing up on Sprint when they should not

Hi there, 

We are currently experiencing this problem where closed issues are showing up on a sprint when the issues were not on the backlog so the user couldn’t have moved it to the sprint. The user started the sprint without these tasks in the sprint container.

They appeared as closed once the sprint started.

We investigated and some of the issues had a change in the sprint value prior to the start of the sprint - there was a change 6 days ago where the the sprint value now included the new sprint name however the user indicated the tasks are not on the backlog so couldn’t have moved it into the sprint.

Is there any way these issues would be added to the sprint then?

We have checked the column configuration of the board and all "green" status are in the correct far right column.


1 answer

1 accepted

2 votes
Answer accepted
Jack Brickey Community Leader Jun 08, 2022

Hi @Drishti Maharaj , being in the backlog isn't a requirement to be able to move an issue to a sprint. If the active sprint is somehow being added to the Sprint field then it will be added. BTW "closed" issues will not generally show in the backlog. Some questions:

  • Which column are these Closed issues appearing?
  • what does the history tab show on these issues? Do you see an entry where the Sprint field is updated and added to active sprint?

Hi @Jack Brickey

  • They are appearing in the far-right column under "done"
  • Yes, I do see the history where the sprint field is changed, however the user states because it was not on their backlog they couldn't have moved it to a sprint (which I suspect is wrong?)


Jack Brickey Community Leader Jun 08, 2022

As I stated above being in the backlog isn't a requirement to appear on backlog and closed issues would not be on backlog. The question is - who or what is updating the Sprint field on closed issues? This should not be happening and should be corrected.

Thank you @Jack Brickey - we will look into it as to why they are changing a closed issue. Much appreciated. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

308 views 0 9
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you