When Story is done but subtask is cancel, Sprint close not allow.

[Moses Lim Him Kuong]

I have a sprint that i'm trying to close but it doesn't allow me to close it.

Story 1(done)- 3 subtask with 1 cancelled, 2 done.

Story 2(in progress) - 3 subtask with 1 done, 1 cancelled, 1 in progress.

Upon clicking complete sprint it prompt that 

Sprint cannot be completed as there are incomplete subtasks on the following issues:

Story 1

I have a cancelled column.

Tried a few ways.

1. filter the board without cancelled.

2. assigning cancelled state to Done in the board.

so far only [2] work. But i want to keep both cancelled and done in the board. Is it possible?

[Nic Brough -Adaptavist- · Accepted solution]

I would be interested to know why your contractor does not recommend the use of the "Select list (cascading)".

It's a standard field in JIRA that has been there for many releases and is very unlikely to be pulled out without Atlassian replacing it with something better (and providing a migration path too)

They may be talking about other addons that provide more advanced cascading selects - these may have worries about future support, but the ones that have been around for a while do not look like they are going anywhere either.

So, the simple answer is probably going to be "use the built in cascading select list", but I'd ask your contractor to expand on their concerns - there might be good reasons that I've not picked up on from your question.

[Huy Pham]

Updated the reason for our contractor recommending against the cascading field. Per your answer I did a search on any issues this field may have had with the Navigator and Gadgets and it seems like most of the fixes to integrate cascading fields better were implemented for JIRA in mid 2013 - early 2014. We've notified our contractor about our decision and he's looking into experimenting with the field some more since his experience with the field was from a few years ago.