How to temporarily stop all Jira automation rules
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
When preparing a stage test environment with production data, we may need to disable all the automation rules temporarily.
Cause
When accessing the Automation list, there is no option to disable all the rules at a glance. You need to manually switch each rule to "disable", and later on, you will need to manually switch again each rule to "enable".
JIRAAUTOSERVER-181
-
Getting issue details...
STATUS
Solution
Option 1: Force the rules to be throttled
Following the Service limits documentation, temporarily set the property "max.processing.time.per.day" (default 3600) to a very small value, like "1", forcing all the automation rules to be throttled.
The rule will start, but as the limit was reached, it will be interrupted.
The limit can be changed using CURL command like the one below, replacing your user, password, and the Jira base URL with valid values:
curl -X PUT -H 'Content-type: application/json' \
-u user:password \
-d '{"key": "max.processing.time.per.day", "value": "1"}' \
http://jirabaseurl/rest/cb-automation/latest/configuration/propertyOption 2: Disable all rules
Disable all rules (Automation for Jira):
update "AO_589059_RULE_CONFIG" set "STATE"='DISABLED'
Where a workaround involves running SQL scripts directly on your database, we strongly recommend you do this first on a non-production, staging or test environment before running the scripts on your production database. We also strongly recommend you take a backup of your data before making any modifications via SQL scripts.
Please note that the above query has been designed for Postgres DB and it may need to be modified as per the DB type.