Identify all automation rules configured for a specific Jira DC project
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Summary
In Automation for Jira, automation rules can be configured to run only in specific projects.
In some instances, it may be helpful to identify all rules configured to run in a particular project, be it for audit purposes or to facilitate administration. This article provides options on how to do just that.
➕ You may also be interested in searching for Automation Rules executed by a specific actor.
ℹ️ We currently have the following feature request to improve A4J's automation search functionality JIRAAUTOSERVER-1109. If this topic interests you, be sure to vote and watch the feature to be informed about future updates.
Environment
Any version of Jira Data Center, Jira Software, or Jira Service Management, with Automation for Jira bundled or installed as a user-installed app.
Solution
Identify rules via the User Interface
In ⚙ > System > Automation rules (global admin), the rule list can be filtered by project scope using the Project filter in the rule list header. This surfaces single-project and global rules but does not show multi-project associations — for a complete project-to-rule mapping, use the database queries below.
The Automation search in Jira only allows administrators to search by rule names; therefore, the only workaround available is to search the Jira database.
Before you run these queries:
These queries read the Automation for Jira app tables directly. Run them read-only against a database user with SELECT access; never run them against a live primary during peak hours on a large instance.
The table prefix AO_589059_ is specific to the bundled Automation for Jira app. If your instance installed A4J as a separate Marketplace app, the prefix will differ. Confirm the prefix first with this query:
SELECT table_name FROM information_schema.tables WHERE table_name LIKE 'AO_%RULE_CONFIG';
SELECT table_name FROM information_schema.tables WHERE table_name LIKE 'AO_%RULE_CONFIG';Option A: Search based on the desired project key
The query below was designed for Postgres database syntax, but it should work for different databases with little to no adjustment.
Database query:
SELECT rc."NAME" AS "Rule Name", rc."STATE", pj.pname AS "Project Name", pj.pkey AS "Project Key"
FROM "AO_589059_RULE_CFG_PROJ_ASSOC" rcpa
JOIN project pj ON rcpa."PROJECT_ID" = CAST(pj.id as varchar)
JOIN "AO_589059_RULE_CONFIG" rc ON rcpa."RULE_CONFIG_ID" = rc."ID"
WHERE pj.pkey = 'ProjectKey';ℹ️ To use this query, change ProjectKey with the actual project key for the project you want to search for.
Option B: Search all automation rules with the entire project association
The query below was designed for Postgres database syntax, but it should work for different databases with little to no adjustment.
Database query:
SELECT rc."NAME" AS "Rule Name", rc."STATE", pj.pname AS "Project Name", pj.pkey AS "Project Key"
FROM "AO_589059_RULE_CFG_PROJ_ASSOC" rcpa
JOIN project pj ON rcpa."PROJECT_ID" = CAST(pj.id as varchar)
JOIN "AO_589059_RULE_CONFIG" rc ON rcpa."RULE_CONFIG_ID" = rc."ID"
WHERE pj.pkey in (select pkey from project);How to verify the results
Cross-check the returned rule count against the Automation audit log for that project (Project settings > Automation > Audit log) — every rule that has executed will appear there. A rule in the query result that never appears in the audit log is configured but has never fired (check its STATE column value ENABLED vs DISABLED).
Was this helpful?