How to Access Jira Automation

If your team is still manually moving tickets, sending status updates, and updating fields by hand — you’re leaving hours of productivity on the table every single week.

Jira automation fixes that. It lets you build no-code rules that trigger actions automatically based on events in your project. No developer needed. No complex setup. Just point, click, and automate.

This guide walks you through exactly how to access Jira automation, where to find it depending on your plan, and how to start your first rule in under five minutes.

What Is Jira Automation?

Jira automation is a built-in feature that lets you create “if this, then that” rules inside your Jira projects. A trigger fires when something happens (like a status change or a new comment), and an action runs automatically in response (like assigning a ticket, sending a notification, or updating a field).

According to Atlassian, teams using Jira automation report saving an average of 3 to 5 hours per person per week on manual task management. Across a team of 10, that’s 30–50 hours recovered every week — time that goes back into actual work.

Some quick numbers that put this in perspective:

• 81% of workers say repetitive manual tasks are a major source of frustration at work (Smartsheet)
• 94% of workers say they perform repetitive, time-consuming tasks in their jobs (Salesforce)
• Teams that automate routine workflows see productivity improvements of up to 20% (McKinsey)
• Jira has over 65,000 customers globally, and automation is one of the most-used features across all plan tiers (Atlassian)

The point: if you’re not using automation in Jira yet, you’re working harder than you need to.

How to Access Jira Automation — Project-Level

Project-level automation applies rules only to a single project. This is where most people start, and it’s the quickest path to your first automation rule.

Step 1: Open your Jira project

Navigate to the project where you want to set up automation. Click the project name from your sidebar or dashboard.

Step 2: Go to Project Settings

On the left-hand navigation panel, scroll down and click Project settings. This is typically at the bottom of the sidebar.

Step 3: Click “Automation”

Inside Project Settings, you’ll see a list of options. Click Automation. This opens the automation library for that project.

Step 4: Create your first rule

Click Create rule in the top-right corner. You’ll be taken to the rule builder where you can choose a trigger, add conditions, and define actions.

That’s it. You’re inside Jira automation.

🚀 Turn Your Pipeline Into Revenue

Stop chasing leads manually. Start booking meetings. Our complete outbound strategy — targeting, campaign design, and LinkedIn + cold email scaling — fills your calendar with qualified prospects. Book Strategy Meeting →

(Right Side Sticky Banner — place this as a fixed element on the right side of the page)

How to Access Jira Automation — Global (Admin) Level

If you’re a Jira admin and you want to create automation rules that apply across multiple projects — or manage all rules from one place — here’s how to access global automation.

Step 1: Go to Jira Settings

Click the gear icon (⚙️) in the top-right corner of any Jira page. This opens the site administration menu.

Step 2: Select “System”

Under the administration menu, click System. This is only visible to users with admin access.

Step 3: Click “Automation Rules”

In the System settings, look for the Automation section in the left panel. Click Automation rules to access the global automation library.

From here, you can create rules that span multiple projects, set global templates, and manage all existing rules across your workspace.

How to Access Jira Automation — Jira Cloud vs. Jira Server/Data Center

The access path varies slightly depending on which version of Jira you’re using. Here’s a quick breakdown:

Jira Cloud

• Project-level: Project Settings → Automation
• Global level: Settings (⚙️) → System → Automation rules
• Available on Free, Standard, Premium, and Enterprise plans (with varying rule limits)

Jira Server / Data Center

• Access: Administration → Automation for Jira (requires the Automation for Jira app — available on the Atlassian Marketplace)
• On older versions of Server, automation may require installing the “Automation for Jira” plugin separately
• Premium and Enterprise Data Center plans include automation natively

Plan-based rule limits on Jira Cloud:

• Free plan: 100 rule runs per month
• Standard plan: 1,700 rule runs per month
• Premium plan: 1,000 rule runs per user per month (uncapped effectively for most teams)
• Enterprise: Unlimited rule runs

If you’re hitting your rule run limits, upgrading your plan or consolidating rules with branching logic can help you stay within caps.

Understanding the Jira Automation Rule Builder

Once you’re inside the automation library and you click Create rule, you’ll land on the rule builder. Here’s what you’re working with:

Triggers

The event that starts the automation. Common triggers include:

• Issue created
• Issue transitioned (status changed)
• Field value changed
• Comment added
• Scheduled (time-based)
• Webhook received

Conditions (optional)

Filters that check whether a rule should continue running. For example, “only continue if the issue type is Bug” or “only if the assignee is empty.”

Actions

What actually happens when the trigger fires and conditions are met. Common actions include:

• Assign an issue
• Transition an issue to a new status
• Send an email or Slack notification
• Create a sub-task
• Edit a field value
• Log work automatically

Branches (advanced)

Branches let one rule handle logic across related issues. For example, when a parent epic is completed, automatically transition all child stories.

Most Useful Jira Automation Rules to Set Up First

Once you know how to access Jira automation, these are the highest-impact rules to build right away:

Auto-assign issues based on type or component

Stop manually assigning every ticket. Set a rule: when an issue is created with a specific component label, automatically assign it to the right person or team.

Auto-transition issues when sub-tasks are completed

When all sub-tasks under a story are marked Done, automatically move the parent story to Done as well. This alone eliminates dozens of manual status updates per sprint.

Send Slack or email alerts on high-priority issues

When an issue is created or updated with Priority = Critical, automatically notify a Slack channel or send an email to the relevant team. No more missed escalations.

Close stale issues automatically

Set a scheduled rule: if an issue has been in “Waiting for response” for more than 7 days with no update, automatically transition it to Closed with a comment. Keeps your backlog clean without the manual audit.

Sync issue status to linked tickets

When a blocking issue is resolved, automatically notify or update the tickets that were waiting on it. Keeps everyone in sync without the ping-pong communication.

Research from Atlassian shows that teams using five or more automation rules see up to 40% reduction in time spent on issue triage and status updates. The more rules you build, the more time compounds back into your team.

Jira Automation Templates — The Fastest Way to Start

You don’t have to build from scratch. Jira’s automation library includes pre-built templates you can activate in seconds.

To access templates:

1. Go to the Automation page (project or global level)
2. Click Create rule
3. Select Browse templates from the rule builder
4. Filter by category (e.g., Agile, DevOps, Service Management) or search by keyword
5. Click Use template, review the pre-filled fields, and save

Popular ready-to-use templates include:

• Auto-close resolved issues after 14 days
• Notify the team when a sprint starts
• Auto-assign issues to reporters
• Sync issue priority with linked Jira Service Management tickets
• Escalate overdue issues to a manager

Templates cut setup time from 10–15 minutes to under 60 seconds for common use cases.

Common Issues When Accessing Jira Automation (and How to Fix Them)

“Automation” doesn’t appear in Project Settings

This usually means you don’t have project admin permissions. Ask your Jira admin to grant you “Administer Projects” permission for that project.

Rules aren’t firing

Check the audit log (available inside the automation rule) to see exactly where the rule stopped. Common causes: conditions not being met, rule is disabled, or you’ve hit your monthly rule run limit.

Can’t see the global Automation settings

Global automation requires Jira site administrator access. If you don’t see it under Settings → System, you need elevated permissions from your org’s Jira admin.

Automation for Jira app isn’t installed (Server users)

On Jira Server, automation is provided by a free Marketplace app called “Automation for Jira.” Go to Administration → Manage apps and search for it. Install, then access it via Administration → Automation for Jira.

Rules running but taking the wrong action

Review your conditions carefully. A missing condition is the most common cause of rules acting on the wrong issues. Add a “Issue matches JQL” condition to tighten your targeting.

Jira Automation Permissions — What You Need

Understanding permissions prevents the most common access headaches:

In Jira Cloud, project admins have full control over project-level automation without needing site admin access. This makes it easy for individual teams to own their own automation without IT bottlenecks.

Conclusion

Accessing Jira automation takes less than a minute once you know where to look. Go to Project Settings → Automation for project-level rules, or Settings → System → Automation Rules for global control.

The bigger opportunity isn’t just knowing how to find it — it’s using it. Teams that invest time in building smart automation rules consistently recover hours of manual work every week, reduce errors, and move faster without adding headcount.

Start with one rule today. Auto-assign a ticket type, close a stale issue, or send a status notification. Once you see it work, you’ll build five more before the end of the sprint.

The best processes are the ones that run themselves.