How to Set Up Automations in Jira (2026 Guide)
Jira Automation is a rule-based engine built into every Jira project. It eliminates repetitive manual work like assigning issues, transitioning statuses, sending notifications, and enforcing workflow rules. Automations run server-side, so they work even when no one is looking at the board.
This guide covers how to set up the most impactful Jira automations for product and engineering teams.
Step-by-step guide
Step 1: Access the Automation engine
Go to Project Settings > Automation. Click "Create Rule" to start building. Each rule has three parts: a Trigger (what starts it), optional Conditions (when to apply), and Actions (what happens). Jira provides a library of pre-built templates for common automations.
Step 2: Auto-assign issues by component
Create a rule: Trigger = Issue Created, Condition = Component = "Backend," Action = Assign to the backend team lead. Duplicate for each component (Frontend, Mobile, Infrastructure). This ensures every new issue has an owner immediately.
Step 3: Auto-transition on PR merge
Create a rule: Trigger = Development > Pull Request Merged (requires GitHub/Bitbucket integration), Action = Transition issue to "In Review." This automatically moves issues through the workflow when code lands, reducing manual status updates.
Step 4: Enforce required fields
Create a rule: Trigger = Issue Transitioned to "In Progress," Condition = Story Points is Empty, Action = Transition back to "To Do" and add a comment: "Cannot start work without a story point estimate." This enforces estimation before work begins.
Step 5: Send Slack notifications for high-priority items
Create a rule: Trigger = Issue Created, Condition = Priority = Highest or Blocker, Action = Send Slack Message to #engineering-urgent with issue summary, link, and assignee. This ensures critical issues get immediate attention.
Step 6: Auto-close stale issues
Create a scheduled rule: Trigger = Scheduled (weekly), Condition = Status = "Waiting for Customer" AND last updated > 14 days ago, Action = Transition to "Closed" with comment: "Auto-closed after 14 days of inactivity." This keeps your backlog clean.
Common mistakes
Too many automations without documentation
Teams add automations ad hoc until no one knows what rules exist or why. Document every automation rule in a shared page. Include: what it does, why it exists, and who owns it. Review automations quarterly.
Automation loops
An automation that changes a field can trigger another automation that changes the same field. Jira has loop detection, but complex chains can still cause unexpected behavior. Test new automations in a sandbox project first.
Replacing communication with automation
Automating everything (auto-assign, auto-transition, auto-close) can remove human judgment. Use automations for routine tasks and enforce rules, but keep human decisions for prioritization and scope changes.
Tips
- Use the Automation Audit Log to debug rules that are not firing as expected
- Start with Jira's pre-built automation templates and customize from there
- Use Smart Values in automation actions to include dynamic data (issue key, assignee, priority)
How Vantage helps
Vantage integrates with Jira's workflow through two-way sync. Tickets generated from PRDs push to Jira and participate in your existing automation rules. Status changes in Jira sync back to Vantage, keeping the PM's view of execution up to date without manual tracking.