Use the Jira automation template library

Still need help?

The Atlassian Community is here for you.

Ask the community

We’ve created a set of pre-defined automation rules that you can use as-is or modify further to meet your needs. You can also view these rules in a safe sandbox environment, which is a copy of Jira automation in your browser.

The automation library lets you:

  • View common use cases that you can apply in your projects

  • View details of rules, including all fields so you can recreate them in Jira

  • Modify rules in a safe environment without risking affecting your Jira projects

Compatibility with Data Center

The automation library is targeted at our cloud users, that’s why you might see references to cloud. Automation in Data Center is mostly the same, so you can still use these templates. We’ve described which rules might work differently or be incompatible in Compatibility with Data Center.

View pre-defined automation rules

To view the pre-defined automation rules:

  1. Go to Automation template library.

  2. Select one of the popular categories or templates, and then select the rule you’re interested in.

  3. The rule will be opened in the Automation Playground where you can view or modify its details.

You can also switch between available rules using the list in the Automation Playground, as shown below:

Recreate the rules in your environment

You won’t be able to import these rules to Jira, but you can recreate them manually. 

Here’s a sample When a story is added to the current sprint > then send email rule with explanations. It should give you an idea of what you need to view and copy to the automation in your project:

  1. When: That’s a trigger. In this example, it’s Field value changed.

  2. If: That’s a condition. In this example, it’s JQL condition.

  3. Then: That’s an action. In this example, it’s Send email.

  4. Main view: This view shows the details you need to copy. In this case, it shows the rule details as that’s the section we’ve selected in the menu on the left. Select triggers, conditions, and actions to view their details and recreate them in your project.

Compatibility with Data Center

Unfortunately, not all automation rules from the library will work in the same way for Data Center. Here you can find the list of rules that aren’t fully compatible:

View the list of incompatible rules...

Rules related to Slack:

These rules can’t be used, because Data Center doesn’t have the Lookup issues action.


DevOps automation rules

These rules can’t be used, because Data Center doesn’t have these triggers:

  • Commit created

  • Pull request created

  • Pull request merged

  • Build failed

  • Deployment failed


Re-open issue if customer comments on a closed issue

Data Center doesn’t have the Is customer option in the user condition.


Auto link related issues

When any Jira issue has been marked as Deployed to cloud then transition it to Done

You can use these rules, but Data Center has fewer configuration options in the Scheduled trigger. You’ll need to adjust to available options.


Email reporter when expense claims have no attachments

Auto-close old Jira support tickets

Sent e-mail notification to the assignee about the task due date

Delete attachments from old issues

Edit security level when a confidential issue is created

This rule uses an ID of a custom field, which is specific to cloud. You’ll need to adjust the ID to a custom field that you want to use.


Last modified on Jun 6, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.