Post Function to Cancel all issue types(subtask,task,bug,story) in JIRA

[Isha Grover]

Please help me to Write post function to cancel all issue types(subtask,task,bug,story) in jira so that on closing the sprint the required issue does show in backlog and sprint can be closed easily. Moreover i also need a solution that will not impact jira-align when issue is synchronized from stra-jira to jira-align.

Please help me at earliest.

[Jack Brickey]

Hi Isha, I don’t understand why you need a post function to close a sprint. You simply need to ensure that your issues are in the far right column in your board. Any issue that are not in that column will remain in the Backlog view as they are not complete. You should also consider ensuring the Resolution field is set which can be done via a post function or manually when closing an issue. Let me know if I am missing something or if you need further assistance. 

[Isha Grover]

When issue is synchronized in jira-align we can face issue that's why we want to write post function to cancel all issue types(subtask,task,bug,story) in jira so that we don't face any issue in mapping to jira -align.

Let me know if you need any further information.

Thanks 

[Jack Brickey]

Sorry, I don’t use Jira Align so likely not the best to offer a solution. That said, what do you mean by “cancel all issue types”. I’m unaware of any concept of canceling issues in Jira. Maybe you have a status named Cancelled. 

[Isha Grover]

yes we have status named cancelled so any solution for this.

[Nic Brough -Adaptavist-]

This is not something you should be automating like this.  "Cancelling" an issue is something a human should always be checking and doing if it is appropriate, not just doing it because something else is done.  Especially when it's done at scale - the only time you don't need a human to check it is when you're cancelling the entire project.

[Jack Brickey]

Thanks for the clarification Isha. I agree with Nic that you might not wish to automate this. Again I don’t use Align and the concept of syncing with Jira is foreign to me. I don’t know if this is a normal expected action and if it is something that happen continuously, occasionally or once. If Once then manual operation is the best approach. Regardless, I would focus on the true issue here. Why does syncing with Jira cause problems and is this something that should be done at all.

[Isha Grover]

But sir we looking for alternative -  that when issue of any type is cancelled it should not appear in backlog and should not stop us from closing the sprint and when the same issue is mapped to jira-align there should be no impact .

So please consider the scenario of mapping issue from jira to jira-align suggest me for the solution.

[Nic Brough -Adaptavist-]

To do that, you should have a person decide that an issue is cancelled and move it into the cancelled status, which you have mapped into a "done" column on the board.

This will feed up into Jira Align automatically, there's no automation needed, you just need to get the process mapped and executed properly.

[Isha Grover]

Thanks sir.