Data Center 10.4
Versions

Examples and use cases of Jira automation rules

Jira Data Center automation

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

robotsnoindex

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

 

Writing an automation rule that fits your use case is not always an easy task, as it might be difficult at time to know where to start.

The purpose of this page is to provide a list of automation rules that covers various area such as basic operations, Jira Software and Jira Service Management automations, integration with external applications, or sending notifications.

Even though these rules might not address your exact use case, they might be used as a good starting point to write your own custom automation rule.

Environment requirements

Starting from Jira Data Center 10.0, we integrated Jira automation (formerly Automation for Jira) as part of Jira Data Center (both Software and Service Management), offering you the convenience of upgrading either through Jira or the Universal Plugin Manager (UPM). To streamline and enhance your experience with Jira automation, we've made the decision to solely offer it as a bundled version starting from Jira 10.0.

This guide assumes that you're using:

  • Jira Data Center 8.0.0 or later
  • Jira automation:
    •  7.4.0 or later for most rules
    • 9.0.1 or later for the rules that are using the Lookup Issues and Create Variable actions

Automation rule templates

Explore the following automation rule examples and use cases:

Basic Jira issue operations

Rule template
Close sub-tasks when the parent issue is closed
Close parent issue after all sub-tasks have been closed
Transition the Parent issue based on the sub-task status
Transition/Close issues that have been in the same status for > X days
Move an issue to a new project
Add components to issues
Clone Tasks/Stories along with their sub-tasks
Sync fields and comments between linked issues
Concatenate comments from an original issue into one comment and copy it into the cloned issue
Copy the value of a field into another field
Update multi user picker fields
Update select fields (multiple choices)
Update group picker fields (multi groups)
Move issues to the Epic issue type from a different issue type
Trigger a rule when a sub-task is moved to a new parent
Add members of a project role to an issue watching list
Prevent or revert field changes using automation rules
Warn a user when the total logged time in a Jira issue exceeded a certain value
Create a Confluence page including Jira issue data
Mention the assignee in a comment
Count the total number of linked issues and copy it into a number field
Validate "Assignable user" permission when cloning issues

Using complex IF/ELSE conditional logic with smart values to convert select list fields into numbers

Prevent user from setting null value for a custom field by setting it back to original value

Count the number of sub-tasks and copy it into a number field

Clear a custom field when cloning an issue

Send a notification email for specific field updates

Jira Software automations

The rule templates listed below provide ways to manipulate fields such as Story Points, Epics, Advanced Roadmap Teams, Parent links:

Rule template
Calculate the sum of story points from Sub-Tasks and copy it into the parent issue (story, task, bug...)
Calculate the sum of story points from Stories and copy it into the linked Epic

Clone Stories (and their sub-tasks) linked to an Epic when the Epic is cloned

Update Epic Status based on Epic Workflow Status Transition

Calculate the ICE score based on filled fields and issue prioritisation for effective backlog management
Close Epics once all child issues are closed

Automation rules related to Advanced Roadmap fields (Parent Link, Team, Target Date...)

Rule template
Calculate the sum of story points from Epics and copy it into the linked Initiative
Close an Initiative (or parent) issue once all its Epics (or child issues) are closed
Update the Advanced Roadmap Team field
Update a story's target start and end dates based on the sprint dates
Update a parent issue (Initiative) based on an update made to its Child issue (Epic)
Trigger a rule when the Parent Link field is populated
Clear the Advanced Roadmap Parent Link field
Copy a field from a Parent to a Child issue when the Child issue gets linked to it
Copy a field from a Parent to a Child issue when this field is updated in the Parent issue 
Add an IF condition checking the content of the Advance Roadmap Team field
Export Advanced Roadmaps fields in Data Pipeline
Clone a Feature issue and its child Epic issues, stories issues and sub-tasks

Jira Service Management automations

The rule templates listed below provide ways to manipulate fields such as Request Participants, Organizations, Customer Request Types:

Rule template
Update the Request Participants field
Update the Organizations field
Clone an issue and update the Request Type field
Send Slack Message with list of issues with SLA due in 1h
Customize the Customer Satisfaction email
Send an email including the last comment along with the customer facing URL of the attachments
Create customer requests on a schedule and share them with groups
Change the visibility of internal comments to public immediately upon creation

Automation Rules related to Insight/Assets fields

Rule template
Copy Assets custom fields when cloning a Jira issue
Copy Assets custom fields values from a parent Jira issue to a subtask

Sending emails to Jira users with custom content

Rule template
Send email from a Jira issue to an email address containing the issue reporter username and a fixed domain
Send email with a numbered list of Jira issues
Send weekly reminder emails for assignee to log work
Send email if assignee has more than X issues in current sprint
Send email with list of issues from completed Sprint
Send email with 2 list of issues (resolved and unresolved) from on an going sprint
Send email with list of issues that have been “in progress” status for longer than 5 days
Send email with list of opened issues per team in an Advanced Roadmap plan
Send email with list of issues from various JSM queues
Send email to the project lead

Integrating with external applications and Jira REST API

Rule template
Integrate with Microsoft Teams
Integrate with Slack
Integrate with Jenkins
Integrate with Jira REST API

Rule scheduling

Rule template
Exclude specific dates from rule scheduling
Rule scheduling based on a Due Date field

Miscellaneous use cases

Rule template
Count the number of times an issue was transitioned to a specific status
Check if an issue was raised during business hours
Append Assignee Full Name to the end of the Summary field
Set the reporter to the user who triggered the rule
Execute an action if a field was changed from an empty value to a non empty value
Shift a date field with the number of days which another date field was modified by
Authenticating OAuth 2.0 for outgoing web requests in Jira Automation rules
How to keep track of the last comment made by an Agent ( in Jira Service Management )

Last modified on Feb 14, 2025

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.