Automation For Jira - Automation rule templates

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

Note that this KB was created for the Data Center version of the product. Data Center KBs 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

Summary

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

This page provides a list of automation rules covering various areas, such as basic operations, Jira Software/Jira Service Management automation, integration with external applications, sending notifications, etc.

Even though these rules might not address your exact use case, they might be a good starting point for writing your own custom automation rule.

Solution

Automation rule templates

Link to each category:

Basic Jira issue operations

Rule template
Add components to issues
Add members of a project role to an issue watching list
Clone Tasks/Stories along with their sub-tasks
Close parent issue after all sub-tasks have been closed
Close sub-tasks when the parent issue is closed
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
Create a Confluence page including Jira issue data
Move an issue to a new project
Move issues to the Epic issue type from a different issue type
Prevent or revert field changes using automation rules
Sync fields and comments between linked issues
Transition the Parent issue based on the sub-task status
Transition/Close issues that have been in the same status for > X days
Trigger a rule when a sub-task is moved to a new parent
Update group picker fields (multi groups)
Update multi user picker fields
Update select fields (multiple choices)
Warn a user when the total time logged in a ticket exceeds a certain value
Mention the assignee in a comment

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 automation

The rule templates listed below provide ways to manipulate fields such as Request Participants, Organizations, and 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
How to create customer requests on a schedule and share them with groups

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 including the list of issues

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

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 )

Updated on September 11, 2024

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Atlassian Support