Jira Automation Rule Safety and Value Review
Check automation rules for loops, noise and unintended changes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review our Jira automation rules. For each rule: trigger, conditions, actions, scope (projects) and owner: [RULES_LIST]. Execution counts and failures if known: [EXECUTION_DATA]. Check for loops (a rule that triggers itself or another), actions that edit many issues at once, notifications that spam, rules with no owner, overlapping rules, rules that depend on a field that has changed, and missing audit logging. Check each risk against the evidence provided; when it is weak say 'possible risk, needs confirmation' and propose a question for the rule owner. Group related risks so one mitigation can cover several. Rate each rule by risk and by value. Return a table, a list of rules to keep, simplify, merge or disable, with mitigations small enough to act on within a sprint (marking those needing a decision from outside the team), and a safe test procedure using a test project [VERIFY]. Do not recommend bulk changes without a backup export.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.