Forums

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

Resolved Issues are being rolled when the sprint ends

Peter Wendler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 6, 2014

We are experiencing an issue where work that has been resolved (but which is not closed) is being rolled automatically into the next sprint. I think it is affecting the velocity charts, as well.

Please help!

2 answers

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 6, 2014
This is exactly what is supposed to happen. Agile considers issues "done" in the done column and only allows done issues in sprints as they close. It tries to be helpful by moving not-done issues into the next sprint because that is what you should do. You need to clear up your understanding of "done", or not create the next sprint until the current one is ended (not-done issues go back into the backlog of you do that)
0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 6, 2014
This is exactly what is supposed to happen. Agile considers issues "done" in the done column and only allows done issues in sprints as they close. It tries to be helpful by moving not-done issues into the next sprint because that is what you should do. You need to clear up your understanding of "done", or not create the next sprint until the current one is ended (not-done issues go back into the backlog of you do that)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events