The need: prevent users from accidentally using the wrong issue type when they clone an issue
As a Jira administrator, you want to simplify the work of your users as much as possible. But accidents can happen, and users sometimes don't realize they are creating a new issue with the wrong issue type.
The solution: present the issue type of Jira issue clones
When the work of an agent is to escalate support tickets as "Bug" issues in development projects, it is especially useful if all repetitive actions, such as selecting the issue type of the copy, can be automated.
With Elements Copy & Sync, you can preset the issue type of your copies, so that your users will never have to do it by themselves.
Tutorial
In this example, we will copy an issue with the key SUP-1.
This guide explains how to configure your recipe so that the copy of this issue can only have the issue type "Bug".
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 Target tab.
4 - In the "Target issue context" section, use the Issue type field to select "Bug".
5 - Click on the Save button.
Result
With this simple configuration, when a user applies the "Escalate ticket" recipe from issue SUP-1, the Copy & Sync issue type selector will be set to "Bug", and no other option will be available for the user.
Need more?
By selecting more than one issue type in the recipe configuration, the user will have the choice between these types when applying the recipe from the issue view. This setting can be particularly useful when you want to leave some choice to the end-user over how issues are copied.
•••