Copying Automation Rules
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
This article will help demonstrate the different options available for copying Automation Rules, including where these changes can be made and the requirements for each type to work seamlessly.
Solution
There are a few different ways to copy Automation Rules between Projects and each one is listed and explained below:
Solution 1:
Using the Scope feature to either:
Share with a Single Project
Share with Multiple Projects
Share with a Project Type
Share Globally
This can be done from the Rule Details section within an Automation Rule.
How To:
Navigate to the Service Project > Project Settings> Automation page - OR - GlobalAutomation page
Select the Name of the rule to open the Rule Details section
The Scope will be listed there as shown below and this can be changed as per needs.
Solution 2:
Using the Copy option on an Automation Rule from the Global Automation page in Settings > System.
How To:
Choose Cogicon (top right) > System
Choose Global automation and find the rule you wish to copy
Hover on the right side of the rule > click ( ... ) > Copy
Select the project location (under Projects) for the copied rule and modify it accordingly (Scope, Name, etc)
Save
Solution 3:
Using the Copy option on an Automation Rule from Project Settings > Automation, selecting Copy under the Actions column.
How To:
Choose Project Settings from the project you are looking to make these changes for
Scroll down to Automation
Once the Automation Rule list shows, on the right side of the rule you wish to copy > click ( ... ) > Copy
Select the project location (under Projects) for the copied rule and modify it accordingly (Scope, Name, etc)
Save
However, what are the factors to consider when choosing one option over the other?
Using the Scope Option | Similarities Between the two | Using the Copy Option |
|---|---|---|
The option to copy or "expand" a rule to other Projects is possible from the Rule Details section (from Scope). All updates made to the Automation Rule will take effect on all Projects, as defined from the Scope in Rule Details. | Both options can be done from the Global or Project level You must ensure that the Fields, Transitions/Statuses, Issue Types, etc. all exist for the Project you are copying to. This is so that the Automation Rule continues to work as expected. For example, if there are any "unique identifiers" in the Triggers, Conditions, Actions of the Rule that don't exist in the "copy to" Project, the rule will error and not work as expected. | This option allows you to make edits to Automation Rules that have the general structure/setup that you want without affecting the original rule. Using this option makes a copy in the "copy to" project and therefore does not affect the original rule. |
Was this helpful?