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

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

JIRA Stories that don't get completed in a Sprint. How to handle those?

Amanda McCauley
Contributor
May 7, 2024

When you have a Story that is not Completed/DONE in the timespan of a Sprint, how do most handle that?  Do you roll the same Story to the next Sprint or do you put it in DONE and create a new one?  Is there a standard process for this scenario?

2 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Efe Obaseki
May 7, 2024

Since the story is uncompleted it will be closed and a new sprint will start immediately because there is no time to waste. Alternatively, the story should be sent back into the Backlog for a thorough refinement and grooming in order to have it complete and then the Sprint will start again whenever the Developers deem it fits and ready. 

Like # people like this
Amanda McCauley
Contributor
May 7, 2024

Thank you so much for the quick response!  Your answer makes a lot of sense :)

raz ilan asheknazi
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!
September 2, 2024

I would rather suggest to label this story as 'leftover' to improve the EE process.

TAGS
AUG Leaders

Atlassian Community Events