Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Closing Sprint and moving issues show as added to Sprint

Brian Taylor
Contributor
July 31, 2019

Closing Sprint and moving issues show as added to Sprint - a user states that they closed the sprint and there were issues that moved to the next sprint, however it shows all of those issues in the sprint report as added to the sprint. 

The issues timestamps appear to show the correct day when they issues were moved to the new sprint as part of the sprint closure, and the user states thy did not change the start and stop time of the sprint.   

Wanted to see if anyone else has experienced this issue and any possible explanation. 

 

Screen Shot 2019-07-31 at 10.47.06 AM.png

 

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 1, 2019

Hello Brian,

I understand that, once you completed your Sprint, some issues were moved to the next Sprint in your board, however, in the related Sprint report the issues are Appearing with an asterisk (*), like it was manually added after the Sprint beginning. Is it correct?

Can you confirm if the date which the issue was moved to that Sprint match the start date of the Sprint?

If they match, I believe the * in the issues will not be a problem to track your reports, however, the only thing that would explain this behavior is:

- When the last Sprint was closed and the screen to transfer the undone issues appeared, the issue was first transferred to the backlog and transferred posteriorly to the next Sprint. In fact, this is a very common mistake since sometimes the default option would be to transfer to the backlog:

Screen Shot 2019-08-01 at 18.35.53.png

Let me know if you still have any questions.

Venkata Ramana Kaza August 10, 2020

Hi there,

While closing a Sprint, letting Jira move open issues to one of the future sprints, is showing such issues as scoped for multiple sprints. See attached image.

Issues_with_multiple_Sprints.JPG

Is there a reason why Jira adds sprints than just updating it? I am under the impression that this messes up the Sprint Report and any custom filters. Hence I move them explicitly to next sprint (through bulk edit), ensure there are no open issues and then close the sprint.

Looking for inputs on what is the best way of handling open issues while closing a sprint.

Thanks & Regards,

Ramana.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events