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 |
Transition/Close issues that have been in the same status for > X days |
Concatenate comments from an original issue into one comment and copy it into the cloned issue |
Jira Software automation
The rule templates listed below provide ways to manipulate fields such as Story Points, Epics, Advanced Roadmap Teams, and Parent links:
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 |
Automation Rules related to Insight/Assets fields
Sending emails to Jira users including the list of issues
Integrating with external applications and Jira REST API
Rule template |
Rule scheduling
Miscellaneous use cases
Was this helpful?