The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Resolved Issues are being rolled when the sprint ends

Peter Wendler1
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!
Get involved
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!

Watch
Like Be the first to like this
401 views

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
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 Champions.
Get recognized
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)
Reply
0 votes
Nic Brough -Adaptavist-
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 Champions.
Get recognized
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)
Reply
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security