Allow project admin to enable/disable a global automation rule for their project

[Maxime Reynier]

Hello,

We  are planning a big data import to our Jira platform from none Jira sources. We created a global rule that will help the project admin with part of this process. But this rule should only be active when the project admin is importing the data at the start of the project, after this phase it should be deactivated.

The only solution that we found so far is to use the multiple project scope for automation rules but it means that jira admins will need to modify the rule twice, first by adding the project in the scope when starting the import, then removing it when the import is finished.

 Copying the project configuration doesn't copy the automation rules set in the source project. Setting the rule as global doesn't allow project admin, without application administrator rights, to enable/disable the rule, and this enable/disable applies to the whole instance not to one project.

Do you have a solution that would allow the project admin to enable/disable the automation rule when they need without the application admin input? 

[Bill Sheboy]

Hi @Maxime Reynier -- Welcome to the Atlassian Community!

Short answer: as this is a one-time need for the import, please ask your project admin to partner with the site admin to make the rule changes, and to disable the rule when done.

Global and multiple-project scope rules are quite powerful and impactful.  This is the likely reason site admin permissions (or higher) are required to configure them: to manage and mitigate risks to the entire site.  A single simple mistake could lead to irreversible data changes.  Thus the expectation is a site admin will take the time and caution needed to handle such rules.  Compare this to a project admin who may only have limited knowledge of the entire site configuration or possible rule impacts.

There is an open suggestion to allow project admins to configure rules with multiple-project scope which includes their own permission levels...or even to add a new permission specifically for this type of rule configuration.  Until any changes are made for that permission, please ask your site admin to help the project admin.

Kind regards,
Bill

[Maxime Reynier]

Hello,

thank you for your answer and for the suggestion.

Best regards

[Calvin]

Hmm I may not be understanding this properly, but the options I can think of are:

1. There is a new functionality coming in to update Automations via API. Maybe that might allow you to enable/disable them, via another automation within the project (might not be available for server though) https://community.atlassian.com/forums/Automation-articles/Automation-Rule-Management-API-is-now-in-Open-EAP-Try-it-out-and/ba-p/3066541#M2008
2. Your Global automation has an if statement at the start where some special work item has the value ENABLED in a field like summary, then it runs/moves forward. If it has the value DISABLED then it doesn't run the rest of the automation. That way the automation is always available but only actually does something when a project user switches that value to ENABLED or DISABLED which a project user would have access to.

[Maxime Reynier]

Hello, thank you for your suggestions, unfortunately these new API functions do not work for Data center it seems. 

Your second suggestion is interesting, I will discuss it with other stakeholder, because we need the solution to be as easily accesible as possible for project admins.