Jira Automation and Notification Schemes
What to know
Automation rules have a trigger (e.g., issue created, field changed, scheduled), optional conditions (JQL or field checks), and actions (edit issue, transition, comment, send email, webhook). Rules can be global or project-scoped, and they run with the permissions of the rule actor. Notification schemes define which events (issue created, updated, commented) send email to which recipients (current assignee, reporter, watchers, groups, roles). Events are fired by workflows and by automation.
Traps
Common pitfalls: a rule's actor lacks permission to perform the action, so it silently fails. Conditions using JQL evaluate against the issue at run time. Notification schemes only send to users who can browse the issue. Automation can loop if an action triggers its own rule; guard with conditions. Also, project-scoped rules may not see issues outside the project.
Rule of thumb
Design rules as trigger, condition, action, and always verify the actor's permissions. Use JQL conditions to narrow scope and add a guard to prevent recursion.
Worked example
When a Bug is created, assign it to the component lead and comment. Trigger: issue created. Condition: issue type = Bug. Actions: assign to component lead, add comment. Ensure the rule actor can assign issues and comment; otherwise the rule fails silently.