How to restrict the possible work types of a clone

The need: prevent users from accidentally using the wrong work type when they clone a Jira work item

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 work type.

The solution: present the work type of Jira 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 work type of the clone, can be automated.

With Elements Copy & Sync, you can preset the work type of your copies, so that your users will never have to do it by themselves.

Tutorial

In this example, we will clone a Jira work item with the key SUP-1.

This guide explains how to configure your recipe so that the copy of this work item 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 Work 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 work item SUP-1, the Copy & Sync work type selector will be set to "Bug", and no other option will be available for the user.

•••