Clean up automation rules
To cleanup automation rules, you must be logged in as a user with the Jira System Administrators global permissions.
Overview of global permissions in Jira
Starting from Jira 10.3.23 or Jira 11.3.8 and later versions, you can perform cleanup actions such as bulk disable or delete for automation rules. In earlier versions, you are limited to scanning and displaying all rules and their optimization areas.
Use Instance optimizer to find and clean up Automation for Jira rules that may be stale, inactive, too complex, or no longer owned by an active user.
Automation rule cleanup scans your automation rules and shows rules that match one or more cleanup recommendations. From the scan results, you can review matching rules and disable or delete selected rules in bulk.
On this page:
Scan automation rules
To scan automation rules:
Go to Administration > System.
In the sidebar, select Instance optimizer.
Open Automation rule cleanup.
Select Scan rules.
The scan creates a point-in-time result set. After disabling or deleting rules, run a new scan to refresh the results.
The scan checks for rules that match these recommendations:
推奨事項 | 説明 |
|---|---|
Too many components | Rules with more components than the configured limit |
Too many branches | Rules with more branches than the configured limit |
High fetched item count | Rules with high fetched item counts from recent execution data |
Stale rules with high fetched item count | Rules with high fetched item counts from recent execution data that have been updated for the last 12 months |
Too many subtasks | Rules that create more subtasks than the configured limit |
Stale rules | Rules that haven't been updated for the configured number of months |
Inactive rules | Rules that haven't executed for the configured number of months |
Inactive or missing users | Rules whose actor or author is inactive or missing |
Configure limits
Automation rule cleanup uses default limits to identify rules that may need review.
limit | 既定値 |
|---|---|
コンポーネント | 130 |
ブランチ | 30 |
Fetched items | 5000 |
サブタスク | 50 |
Stale rules | 12 months since last update |
Inactive rules | 6 months since last execution |
To change these limits, open Automation rule cleanup, then select Configure Automation rules cleanup.
We don’t recommend adjusting default limits in production instances without consulting Atlassian support. The default limits are optimized for performance.
Review and filter results
After a scan finishes, Instance optimizer shows the matching automation rules and the top recommendations.
You can filter results by:
ルール名
ステータス
作成者
Actor
プロジェクト
カテゴリ
createdDate
最終更新
Last executed
Disable or delete rules
You can select up to 1,000 rules for cleanup at a time. Selected rules can be disabled or deleted.
Before deleting rules, we recommend exporting them from Automation for Jira. Deleted rules can't be recovered from Instance optimizer.
A cleanup action adds audit log entries when the cleanup starts and when it completes.
To change the maximum cleanup count, set this property in your Jira home directory’s application property file, then restart Jira: jira.optimizer.plugin.a4j.cleanup.max.rules. The value is capped at 5,000 per cleanup.
Scheduled scans and notifications
Automation rule cleanup includes a preconfigured scan and notification schedule:
タスク | Default schedule |
|---|---|
Scan | Weekly on Sundays at 1:45 AM |
通知 | Weekly on Mondays at 8:00 AM |
To update the schedule, set the following property in your Jira home directory’s application property file, then restart your Jira:
jira.optimizer.plugin.a4j.scan.cron controls the scheduled scan cron.
jira.optimizer.plugin.a4j.notification.cron controls the notification reset cron.
By using a cron expression, you can specify exactly when the scan occurs or when the notifications are sent. For example, the default value 0 0 8 ? * MON schedules notification to be sent every Monday at 8:00 a.m.
To toggle notification, open Automation rule cleanup, then select Configure Automation rules cleanup.
