The need: make sure parent and clone issue fields are the same
Sometimes, new information may come up and unexpected changes can happen. But what if your original issue has already been duplicated several times with what is now outdated or incomplete information?
The solution: synchronize changes in the original issue to any clones made
With Elements Copy & Sync, you can fully customize how an issue and its copies are synchronized. With a simple configuration, you will be able to select which fields must be synchronized so that, if the original issue is updated after the copy, the new values will be echoed automatically in all the copies.
Tutorial
In this example, we will copy an issue with the key SUP-1.
This guide explains how to copy all the fields from SUP-1 and synchronize their respective values with the copied issue.
Prerequisites
A recipe called "Escalate ticket" has been created, activated, and is available on issue SUP-1.
Configuration steps
1 - As a Jira administrator, go to the "Elements Copy & Sync Cloud" administration and click on Recipes in the navigation bar.
2 - In the Recipes listing page, select "Escalate ticket" in the Active Recipes list.
3 - In the Recipe configuration page, click on the Content tab.
4 - In the "Fields" section, activate the Set and synchronize fields option. The "Fields mapping options" subsection is displayed.
5 - Click on the "..." button at the right of the Add target fields option, and select Add all available fields.
At this point, all the available fields are added to the Fields mapping table.
6 - Click on the Sync all fields button below the Fields mapping table, in order to activate the synchronization between the source and target issues. You can also use the toggle button in the "Synchronized" column to add or remove fields from the scope of the synchronization.
7 - Click on the Save button.
Result
With this configuration, when a user applies the "Escalate ticket" recipe from issue SUP-1, the fields of the new copy will be synchronized with the fields from SUP-1, meaning that if, for example, the Description of SUP-1 is updated, the same value will be echoed to the copied issue.
•••