Automation that applies to all projects (present and future)

[Radu Ichim]

Hello Community,

I have the following scenario:

In my instance there are multiple projects, and the number will only keep growing. I am trying to build an automation that:

• Checks if issue type Configuration Box has a No value for field Code Test Needed
• If the above matches, the automation should check if this project has any issues of Code Test type and delete them

I managed to set up the first part

- Manual trigger
- Issue Type equals Configuration Box
AND
- Code Test Needed equals No

However, I am not sure exactly how to make sure that what follows now, is that the automation only check in this specific project for Code Test issues, and not in the whole instance.

I need this rule to run project by project, and am not sure if I need some kind of branching that I need, and how exactly to make this a global rule, rather than set it up in each project.

Any suggestions are welcome.

Thank you

[Bill Sheboy]

Hi @Radu Ichim 

Short answer: in my opinion, a rule like this could be quite risky and perhaps the teams could instead investigate how to prevent adding those issues rather than deleting them with an automation rule.

Back to the specifics of your question...

First, you appear to be using Jira Cloud.  Is that correct?  If so, there is no "undo" capability for deleting issues.  Instead I recommend closing the issue with a Resolution value such as "Abandoned" or adding a custom field to indicate this condition.  This will allow recovering such issues more easily when a mistake is made.  You may also want to discuss with your Jira Site Admin disabling the permission to delete issues for everyone except Site Admin, or higher, roles.

Next, when do you want to check for this condition:

• when new issues are created of type Configuration Box
• when the value changes for "Code Test Needed"
• when someone incorrectly sets the value of "Code Test Needed"
• when new issues are created of type Code Test
• etc.

The different conditions could lead to multiple rules (for immediate actions) or more complicated rules when scheduled triggers are used with JQL to identify the issues (when updates are once per day).

Finally, when using Jira Cloud, what is your Jira license level: Free, Standard, Premium, or Enterprise?  The automation usage limits are different for each level (and the number of Atlassian products included).  And so using a generic global rule like this could easily consume monthly usage limits, prevent execution of all other rules on the site.

Kind regards,
Bill