Rolling over incomplete user stories...


we've observed some inconsistent behaviour in JIRA Agile 6.3 when finalising a sprint with incomplete user stories.  I always thought that incomplete stories were placed into the Product Backlog - which is supported by the documentation, however one of our ScrumMasters had observed within his project that JIRA was automatically shifting them into the next open sprint - until recently when it seems to have started placing them into the Product Backlog.

My online searches for an answer to this have been inconclusive.

Can anyone tell me, or point me towards a definitive answer as to JIRA Agile's correct behaviour - and more specifically, how we can ensure it consistently rolls over incomplete stories into the next sprint?




1 answer

1 accepted

0 votes
Accepted answer

I think I found the answer myself.

Remembering that Sprints can be have (at least) 3 statuses:

  • Created
  • Started
  • Closed

So, when the future sprint has been Created (but not yet started) it will automatically rollover the incomplete stories into the new sprint - however if you close the first sprint after having already started the 2nd print it will push them back into the Product Backlog.

Makes some kind of sense I suppose.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,086 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you