# Jira Workflow Automation: How to Automate Repetitive Tasks and Save Hours July 29, 2026 · 6 min read [NGPilot](https://ngpilot.com) Quick Answer Jira automation rules eliminate repetitive tasks like assignment, notifications, and status transitions. Use triggers, conditions, and actions to build rules without code. What you'll learn 1. How to identify which Jira tasks are good automation candidates 2. How to build automation rules using triggers, conditions, and actions 3. How to test, debug, and refine automation rules 4. How to scale automation across projects and teams Every Jira team has repetitive tasks: assigning bugs to the QA lead, transitioning issues when a pull request is merged, sending notifications when a sprint starts. These tasks follow consistent rules, which makes them perfect for automation. Jira's built-in automation engine lets you create rules without code. This guide covers how to identify automation candidates, build rules, and scale them across your organization. ## Why Automate Jira Workflows[​](#why-automate-jira-workflows "Direct link to Why Automate Jira Workflows") Manual processes are slow, error-prone, and do not scale. Automation fixes this: **Consistency.** Rules execute the same way every time. No more forgotten assignments or missed transitions. **Speed.** Automated actions happen instantly. No waiting for someone to manually update an issue. **Enforcement.** Automation ensures process compliance. If the rule says bugs go to QA, they go to QA — no exceptions. **Scale.** One rule can manage thousands of issues across multiple projects. Manual processes cannot. ## How to Identify Automation Candidates[​](#how-to-identify-automation-candidates "Direct link to How to Identify Automation Candidates") Look for tasks that meet these criteria: **High frequency.** If you do it more than once a day, automate it. **Consistent rules.** If the logic is "when X happens, do Y," it is a candidate. **Low judgment.** Tasks that do not require human decision-making are best for automation. **Time-consuming.** If it takes more than 2 minutes each time, automation saves significant time. **Common automation candidates:** | Task | Trigger | Action | | --------------------------- | --------------------------------- | ------------------------------------------- | | Assign bugs to QA lead | Issue created with type = Bug | Assign to @qa-lead | | Notify team on sprint start | Sprint started | Send Slack/email notification | | Move issue to "In Review" | Pull request merged | Transition to "In Review" | | Close stale issues | Updated > 30 days, status = Open | Transition to "Closed" | | Create sub-tasks | Story created with type = Feature | Create "Design" and "Code Review" sub-tasks | ## How to Create Jira Automation Rules: Step-by-Step[​](#how-to-create-jira-automation-rules-step-by-step "Direct link to How to Create Jira Automation Rules: Step-by-Step") ### 1. Access Jira Automation[​](#1-access-jira-automation "Direct link to 1. Access Jira Automation") 1. Go to **Project Settings > Automation** 2. Click **Create Rule** 3. Choose a trigger from the list 4. Add conditions to filter when the rule applies 5. Add actions to define what happens 6. Name and enable the rule ### 2. Choose a Trigger[​](#2-choose-a-trigger "Direct link to 2. Choose a Trigger") Triggers start the automation. Common triggers: | Trigger | When It Fires | | --------------------------- | --------------------------------------- | | Issue created | When a new issue is created | | Issue updated | When any field changes | | Status changed | When an issue transitions | | Sprint started/ended | When a sprint begins or completes | | Pull request created/merged | When linked to a Jira issue | | Schedule (cron) | At a specific time (daily, weekly) | | Webhook | When an external system sends a request | ### 3. Add Conditions[​](#3-add-conditions "Direct link to 3. Add Conditions") Conditions filter when the rule applies. Without conditions, the rule fires on every trigger. **Common conditions:** * **Issue type** = Bug, Story, Task * **Priority** = High, Medium, Low * **Status** = Open, In Progress, Done * **Project** = Specific project * **Field value** = Contains specific text **Example:** Only apply when issue type is Bug AND priority is High. ### 4. Add Actions[​](#4-add-actions "Direct link to 4. Add Actions") Actions define what happens when the trigger fires and conditions are met. **Common actions:** * **Assign issue** — to a user, role, or round-robin * **Transition issue** — move to a specific status * **Send notification** — email, Slack, or in-app * **Update field** — set priority, labels, components * **Create issue** — linked issue or sub-task * **Add comment** — automated note on the issue ### 5. Test and Refine[​](#5-test-and-refine "Direct link to 5. Test and Refine") Before enabling, test the rule: 1. Click **Run rule** with a test issue 2. Check the audit log for results 3. Verify the action was applied correctly 4. Adjust conditions if the rule fired incorrectly 5. Enable the rule when satisfied **Audit log location:** Project Settings > Automation > Audit Log ## 10 Useful Jira Automation Rules[​](#10-useful-jira-automation-rules "Direct link to 10 Useful Jira Automation Rules") ### 1. Auto-assign bugs to QA lead[​](#1-auto-assign-bugs-to-qa-lead "Direct link to 1. Auto-assign bugs to QA lead") ``` Trigger: Issue created Condition: Issue type = Bug Action: Assign to @qa-lead ``` ### 2. Notify team on sprint start[​](#2-notify-team-on-sprint-start "Direct link to 2. Notify team on sprint start") ``` Trigger: Sprint started Action: Send email to sprint-team@company.com ``` ### 3. Move to "In Review" when PR is merged[​](#3-move-to-in-review-when-pr-is-merged "Direct link to 3. Move to \"In Review\" when PR is merged") ``` Trigger: Pull request merged Action: Transition to "In Review" ``` ### 4. Close stale issues after 30 days[​](#4-close-stale-issues-after-30-days "Direct link to 4. Close stale issues after 30 days") ``` Trigger: Schedule (daily) Condition: Status = Open AND updated <= -30d Action: Transition to "Closed" + add comment "Auto-closed due to inactivity" ``` ### 5. Create sub-tasks for new stories[​](#5-create-sub-tasks-for-new-stories "Direct link to 5. Create sub-tasks for new stories") ``` Trigger: Issue created Condition: Issue type = Story Action: Create sub-task "Design Review" + Create sub-task "Code Review" ``` ### 6. Set priority based on summary keywords[​](#6-set-priority-based-on-summary-keywords "Direct link to 6. Set priority based on summary keywords") ``` Trigger: Issue created Condition: Summary contains "urgent" or "critical" Action: Set priority to "High" ``` ### 7. Notify reporter when issue is resolved[​](#7-notify-reporter-when-issue-is-resolved "Direct link to 7. Notify reporter when issue is resolved") ``` Trigger: Status changed to "Done" Action: Send email to reporter with resolution details ``` ### 8. Add label for specific components[​](#8-add-label-for-specific-components "Direct link to 8. Add label for specific components") ``` Trigger: Issue updated Condition: Component = "Backend" Action: Add label "backend-team" ``` ### 9. Transition parent when all sub-tasks are done[​](#9-transition-parent-when-all-sub-tasks-are-done "Direct link to 9. Transition parent when all sub-tasks are done") ``` Trigger: Sub-task transitioned to "Done" Condition: All sub-tasks of parent are "Done" Action: Transition parent to "Done" ``` ### 10. Weekly summary email[​](#10-weekly-summary-email "Direct link to 10. Weekly summary email") ``` Trigger: Schedule (weekly, Friday 4pm) Condition: Status = "In Progress" AND assignee = currentUser() Action: Send email with list of open issues ``` ## FAQ[​](#faq "Direct link to FAQ") ### What can I automate in Jira?[​](#what-can-i-automate-in-jira "Direct link to What can I automate in Jira?") You can automate issue assignment, status transitions, notifications, field updates, linked issue creation, sprint management, and more. Any action that follows a consistent rule can be automated. ### How do I create a Jira automation rule?[​](#how-do-i-create-a-jira-automation-rule "Direct link to How do I create a Jira automation rule?") Go to Project Settings > Automation > Create Rule. Select a trigger (e.g., issue created), add conditions (e.g., issue type = Bug), and add actions (e.g., assign to QA lead). Save and enable the rule. ### Can I automate across multiple Jira projects?[​](#can-i-automate-across-multiple-jira-projects "Direct link to Can I automate across multiple Jira projects?") Yes. Global automation rules apply to all projects. Project-specific rules only apply to that project. Use global rules for organization-wide standards, project rules for team-specific workflows. ### How do I debug a Jira automation rule that is not working?[​](#how-do-i-debug-a-jira-automation-rule-that-is-not-working "Direct link to How do I debug a Jira automation rule that is not working?") Go to Project Settings > Automation > Audit Log to see when rules fired and what actions were taken. Check for conditions that are not met, trigger issues, or permission problems. ### Are there limits to Jira automation rules?[​](#are-there-limits-to-jira-automation-rules "Direct link to Are there limits to Jira automation rules?") Jira Cloud has limits on the number of rules and executions per month based on your plan. Jira Server/Data Center has no hard limits but performance depends on your infrastructure. Monitor usage to avoid hitting limits. ## Related guides[​](#related-guides "Direct link to Related guides") * [How to Plan Jira Sprints That Actually Work](/blog/plan-jira-sprints-that-actually-work.md) * [How to Set Up Jira Dashboards for Sprint Tracking](/blog/jira-dashboard-sprint-tracking-setup.md) * [Jira Permissions Explained: Project Security Setup](/blog/jira-permissions-explained-project-security-setup.md) ## Related guides * [How to Create Mermaid Diagrams in Jira](/blog/how-to-create-mermaid-diagrams-jira.md) * [Export Jira Issues to Excel or CSV](/blog/export-jira-issues-to-excel.md) * [Bulk Download Jira Attachments](/blog/bulk-download-jira-attachments.md) * [How to Migrate Confluence Content](/blog/how-to-migrate-confluence-content.md) Explore NGPILOT[Browse Solutions](/solutions.md)[All Apps](/apps.md)[Atlassian Marketplace →](https://marketplace.atlassian.com/vendors/1226848/?utm_source=ngpilot.com\&utm_medium=blog\&utm_campaign=hub-links) **Tags:** * [jira](/blog/tags/jira.md) * [automation](/blog/tags/automation.md) * [workflow](/blog/tags/workflow.md) * [how-to](/blog/tags/how-to.md) * [productivity](/blog/tags/productivity.md)