Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for Jira throwing errors when Issue Deleted


I have a rule using the plugin that:

- identifies an issue based on Customer Request Type;

- clones specified issue into a different project;

- deletes the original issue. 

The rule works fine, but every time it is triggered I get multiple error emails for other, non-related rules. 

Most of the errors are for rules that send notifications if a specified field is changed (ie Priority changed to Escalated from Normal). Like below: 


I have full permission to this project.

Any idea how I can prevent these errors from occurring? 

2 answers

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 21, 2021

My first guess would be that the successful rule is triggering other rules. I would suggest closely examining the rule that is throwing the error to see if you can understand why it is a triggering. It may be that you simply need to add some new conditions to those rules that are throwing the error so that the rule exits. 

Unfortunately this is not an option in Jira Cloud.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 26, 2023

@Henry Yei , what isn't available in cloud?

I was referring to lukec's fix "Execute this rule immediately when the rule is triggered". There is no dropdown for the Created Ticket trigger in Jira Cloud. I guess I posted this in the wrong reply thread.

I have the same issue in Jira Cloud where I have an automation that deletes tickets automatically created by Firebase Crashlytics, but were generated by a special dev build(based on description content - version). However I have many other automation rules which are setup to be triggered by other rules that handle removing/adding labels we use to triage tickets which get kicked off and then immediately error out because the ticket has been deleted.

The error "Actor does not have permission to view one or more issues, or the issue was deleted (please check permissions and issue security levels):", make it sound like there is nothing I can do with these rules other than ignore failures, since  doesn't sound like these rules even have a chance to start executing the conditional parts.

After explaining myself, I realized that these rules are being triggered by the Firebase integration creating the ticket, not the rule deleting the ticket, so I will look there to see if I can do what you suggest.


Without overcomplicating each rule though, I am not hopeful for a solution other than turn off error notifications for the rules that I think are robust and just living with the others. (some are pretty complicated, and i need to fix corner cases as they crop up).

Jack, thanks. I found this drop down in the Issue Created trigger : 

Execute this rule immediately when the rule is triggered, instead of in the background

Enabling this stopped the error emails. 

Suggest an answer

Log in or Sign up to answer