It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Random "Done" Issues Showing Up in New Sprint Once Sprint is Started Edited

Hi! We have a team who experiences random old issues being added to their new sprints in Jira as soon as they select "Start Sprint". None of the issues were in their project Backlog prior to suddenly appearing in their new sprint. 


Many of these issues are from months ago and are in Done or Cancelled status. Some have a value in the Resolution field and some do not. I've noticed a few of them have open subtasks but most of them do not. Has anyone else experienced this and found a resolution? I'm stumped!

2 answers

0 votes
Brant Schroeder Community Leader Oct 28, 2019

Keilah - The only way I know of that this can occur is when you complete a sprint, move the tasks that are not completed to the next sprint.  In between starting the new sprint individuals close the parent task leaving the sub-tasks open or close the issue already associated with the Sprint.  Then when you create the sprint the sub-tasks and completed issues will appear.  

Most of the stories that were pulled into the new sprint did not have any tasks or other stories associated with them. 

Brant Schroeder Community Leader Oct 31, 2019

Keilah,

They do not need to have any task or story associated with them to be pulled in.  All that needs to happen is you need to add them to the next sprint at the close of the sprint and then someone closes the issue before the sprint is started.

0 votes
Joe Pitt Community Leader Oct 29, 2019

Everything in Done status should have a resolution. That may be part of the problem

Most of the issues did have some value in the Resolution field. Many of them had a Resolution and did not have other stories/tasks associated with them so I'm not sure what else could cause them to be pulled into a new Sprint.

If an issue in category Done is removed from a completed sprint could that cause it to automatically be placed in your new sprint? Several of the issues that were added showed in their Activity that they were removed from a sprint at some point prior to the new sprint being created. 

Suggest an answer

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

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

273 views 1 2
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