Done vs. Canceled

[WurmPeter]

Hello,

The app works great as it is, but we have a hard requirement that seems not to be compatible with "Issue Status Helper":
When an issue gets the status "canceled" (which is another status of the statusCategory "Done") all issues below should also be set to "canceled" (so that it's enough to cancel the upper most issue in the hierarchy to stop any related work).

Imagine task A has subtasks B and C. I have the status "Todo", "In Progress", "Done" and "Canceled":
When task A gets cancelled, my automation cancels subtask B and subtask C.
See what happens in the attached video (sorry for the music).
I guess the cancelling of the subtasks sets their end date and that triggers that the parents status is changed. As the app doesn't know "canceled" it sets the status to whatever it knows, right?

Aufzeichnung.2025-10-24.172337.mp4

[draperd]

Yes, this is a reasonable assumption and something that could be added with some additional configuration. It's an interesting problem because it does require the app to be given additional context. There are many different statuses that could mean that something is "not done and won't be done" (Cancelled, Duplicate, Won't Fix, Not a bug, etc. etc) and I sometimes think that Jira could benefit from a 4th status category to capture this.

The application could conceivably have an additional configuration that allows you to select any status that should cause children to move to another status. Again, this is something I definitely can see the value in adding.

One of my personal frustrations with the current behaviour is that if I decide to cancel a task then the parent is moved to in progress even though it's not really been started, and this also ties into this behaviour.

There is always a challenge between simplicity (for ease-of-use, quick to get started) and complexity (flexibility and power)... I'll have a think about this area more because you're right to point out this as a drawback.

Again, super valuable feedback and I appreciate you providing it.

[draperlassian]

Just a quick update on this... I've made some changes and I'm nearly there with this. I would have liked to have released this today, but there are still a few minor bugs I've got to iron out. Hopefully I can get this out later this week though. Thanks

[WurmPeter]

Take your time. Better late than wrong.

[draperlassian]

I've now released a new version of the application that supports these features (along with a few other changes):

• "Issue" changed to "Work Item" throughout the application
• Improved UX around project specific overrides to make it clear what each project is doing (I'll be adding more of these over time!)
• Cancellation logic handling (configured cancelled status does not start parent, cancelling a parent cancels children)
• New behaviour is OPT-IN for backwards compatibility

At the moment you can only configure ONE status to represent cancellation, this might still be a limitation for some workflows.

[WurmPeter]

Seems to be working as intended. Nice work.

I hope I'm not opening a new can of worms:
Given that from task A (which is in "in progress"), subtask B is "in progress", and subtask C is "cancelled". Then subtask B is set to "Done".
Should task A remain "in progress" (what it does currently) or be set to "Done"?