How would I stop an automation when the issue has been deleted?

[Aubrey Holland]

I have a simple automation that you can see below. When an issue in my DEV project transitions to the DONE status, it adds a comment and changes the status on linked issues in my SUP project. I just got an error, also shown below, where the automation was run against an issue in the DEV queue that had been deleted, and I would like to prevent this error.

Is there a way that I can add a condition or something else to end the automation when the issue it is running on has been deleted? Thanks!

[Dave Mathijs]

Hi @Aubrey Holland welcome to the Atlassian Community!

Yes, in case of a deleted issue, the automation will run into an error.

But why would you want to change the automation rule?

Do you delete that many issues so often?

[Aubrey Holland]

I only want to change the automation rule in order to avoid this error. I don't think we delete issues very often, but it looks like people do or I wouldn't have gotten the error. I suppose we could stop deleting issues, but it seems like the automation ought to be able to handle this.

[Gary Spross]

I'm having the same issue with some of my automation rules. Honestly, Atlassian should handle this in the background and not allow an automation rule to trigger if the issue it's running against no longer exists. As a backup, there should be a check that can be added to have the automation stop running if the issue no longer exists.

[Amit_Shiloach]

We decided to prevent users from deleting issues by adding a 'Cancel' status, allowing them to transfer tickets there instead. Additionally, you can set up an automation to delete all issues in the 'Cancel' status once a week, for example.