Sprint should not close when Sub tasks open

[Narsha Bac]

Hello,

I want to be able to 'not able' to close sprint when sub tasks are still open in that sprint.

When I am closing a sprint with open sub tasks, it is letting me close it. When doing some tests I got a message "cannot close sprint as there is one sub task open" once. However when trying to replicate this, it is not giving me the message and the sprint is closing.

Help please. I really need this is to work.

Thanks,

Narsha

[JM Perrot · Accepted solution]

Hello @Narsha Bac ,

It's difficult to answer to your problem without context but maybe I can try.

You should have all your end statuses (green statuses) in the last column and only those statuses.

If it's all, perfect, else let me know,

Regards,

JM

[Narsha Bac]

Hi JM,

My statuses are all mapped correctly to the columns needed. I also have my end status at the end.

To give you some context: I need to be able to restrict the closure of a sprint if there are any sub tasks still open. When doing some tests, I got the message once where it prevented me to close the sprint as there was still a sub task open. 

However, when doing this again it is allowing me to close the sprint. Maybe I am doing something wrong?

Thanks,

Narsha

[JM Perrot]

Hi Narsha

I may have an answer, is the parent ticket of the subtask in an open status?

Subtasks are not sprint items, they are parts of a parent ticket.

So when the parent ticket is finished but the child ticket is not, you can't close the sprint (illogical position of the subtask), but if the parent ticket is "open" and the subtask is also open, you can close the sprint and choose to send these tickets in the backlog or in the next sprint.

Regards,

JM

[Narsha Bac]

Hi JM,

Thanks! I tested it based on what you said and it worked.

Regards,

Narsha

[Frederik Vantroys]

I had problems myself in the past when closing sprints that have issues or sub tasks whose status is not mapped to a colum on the sprint board.

Maybe that's where something goes wrong for you too :

In board settings check column section and make sure all  (used) statuses are mapped to a column.    Anything in unmapped status column can pose a problem.

[Narsha Bac]

Hi Frederik,

Thanks for your response. Unfortunately this is not the case for me as my statuses are mapped correctly.

Regards,

Narsha