nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation for Jira throwing errors when Issue Deleted

lukec_fnk0wx

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?

Accepted answers

Jack Brickey_h10pa4

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.

All comments

Jack Brickey_h10pa4

lukec_fnk0wx

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.

Henry Yei_fexq30

Unfortunately this is not an option in Jira Cloud.

Jack Brickey_h10pa4

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

Henry Yei_fexq30

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).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

automation