Disable Automation for Jira Software without impacting Jira Service Management

[Richard Cross]

It seems Automation for Jira is no longer optional in Jira 9.4, and I'm extremely concerned at the potential performance impact of suddenly allowing 3,066 projects to be able to set up rules that trigger on issue creation, update, etc. on a system with 3.4 million issues and 20,000 users.

I tried disabling the Automation for Jira plugin, which is now a system-level app, but this also disables both Automation menu links in Jira Service Management projects ("Automation" and "Legacy Automation").

With the plugin disabled, I can fortunately still access the Legacy Automation via the URL:  https://<jira server url>/servicedesk/admin/<project id>/automation

However, that Legacy Automation feature is due to be deprecated.

Is there a way to allow the new Automation engine for Service Management Projects only?

[Trudy Claspill]

I have not found the answer to your specific question, but an alternative is to restrict the ability to create Automations to only Jira Administrators.

https://confluence.atlassian.com/automation070/permissions-for-project-automation-1014664488.html

You could create a special user group for your Service project admins so that they could still make Automation rules if that was desirable.