Tickets inherited from sprint to sprint

[Julian Albino]

Hello,

After a long and unsuccessful research, i'm asking for help for a problem about tickets inherited from sprint to sprint.

Let me put the context : i'm working with several persons on a web agile project and we are using Jira to manage our sprints.

There are some tickets that we add to a sprint and finish in a following sprint. When the sprint is closed, some of these tickets (which are finished) are moved to the next sprint with the unfinished tickets.

I still don't understand why some tickets have this behaviour and why some others don't. Some of them are part of an Epic, some of them don't. But they all have the status Done.

Can you help me ? I'll try to answer your questions if you have any.

Thank you for your help.

[Nic Brough -Adaptavist- · Accepted solution]

Sprint issues only move to the next sprint when they are not done.

The definition of done in a Jira sprint board is "the last column", with a slight addition that issues with open sub-tasks also count as not done even if they are in the last column.

The Epics and other associated data is not considered here, it really is just the very last column on the board for issues at the story level.  So I would want to take a close look at an issue that has jumped into the next sprint when you closed the sprint.  Was it definitely in the last column when you ended the sprint?  Did it have any open sub-tasks?

[Julian Albino]

Done is the last column in our workflow and most of the tickets don't even have subtasks.

[Nic Brough -Adaptavist-]

You have answered your own question here!

"done" is not the last column.  "Validated" is the last column, and all the other status in your workflow mean "not done" because they are not in that column (whether in other columns or not mapped, they're not done because they're not in the last column)

You'll need to map your done status into the "validated" column, or, more likely, create a proper column for (actually) "done" to the right of "validated"

[Julian Albino]

The fact that we had several Kanban views made me think it wasn't linked to the column but only to the workflow. Thanks to your comment, we noticed that we have a main Kanban view, the one without the Done column !

Our sprint ends in 15 days, we'll see if this fixes our issue. Thank you both for your help !

[Trudy Claspill · Accepted solution]

Jira will consider the issue "complete"  if it is in the right-most column of the board when you use the Complete Sprint feature, and if all the sub-tasks of the issue are also in the right-most column, regardless of what status is mapped to that column.

Are your "done" issues all in the right-most column of your board?

[Julian Albino]

Yes, and Done is the last status in our Workflow : 

[Trudy Claspill]

Can you show us the Column/Status mapping for your board and provide an example of an issue that was in that column but got moved to the next sprint when the current sprint was completed?

[Anthony]

Hello, 
I am not sure to understand what do you mean by "Column/Status mapping". 

• Here is the "board settings" > "column" tab :
  
  
  

• example of an issue : 
  
  As you can see, the US was none on 27 July, and the sprint was closed August 11th, but the US was moved to the new sprint :S 
  
  The US wasn't on the last column, because we dont show the Done tickets in our kanban. 
  Is it the reason why ? it would be a suprise because some tickets are not report to the next sprint when they are done ... 

[Trudy Claspill]

Yes, because you do not have the status Done mapped to the right-most column on your board, issues that are in the Done status will be considered incomplete and the end of the sprint and you will be prompted to move those to the next sprint or the backlog.

[Anthony]

Great, 
we'll see at the end of the next sprint if it works


thanks for your help 

[Julian Albino]

The sprint ended and it worked ! 

Thank you guys for your help !