Sprint closure with dropped tasks

unknown

In my project, initially I configured the active sprint columns  as pending, ongoing, dropped  and done( 4 columns). However with this configuration, the sprint closure is not possible. Sprint is not allowed to close with tasks/subtasks under dropped column ! Strange.

Then after, I merged dropped in to done with 3 column configuration, then the closure is possible. The concern is, the drag and drop is bit tricky. Engineers by mistake drop their sub tasks to dropped instead of done as both are configured in the same column. 

My question is can you program to allow closure of sprints with a dedicated "dropped" column having tasks in it?  

 

sudarshan_x34rab

Hello @[deleted]
I understand your problem when engineers do the by mistake act and it can be educated.

A sprint cannot close with open subtasks for an issue.
Can you check your workflow and how your status are managed.

If your workflow needs such a setup then try the API, but here is what i would do.

For the dropped column -- I add a status called Cancelled, and this resembles a done status in the workflow (meaning it is in green), and you can close your sprints and things will look neat.
Guide your Engineers to push an issue to the dropped column when it has tobe cancelled (set your workflow status to transition all for the Cancelled status)

check out the jira Status documentation

and if you are looking to customize your sprints you can try it out with the Jira REST API

https://docs.atlassian.com/jira-software/REST/7.3.1/
There is one to update the sprint. (check the methods under Sprint), with this you can add your logic and try it out. (i have not tried it)

Hope this helps you!