The need: create multiple issues at once

Employee onboarding, project launches, new customer set-up, change management...Many processes require multiple Jira issues, and the same group of issues every time. Each of these issues contains some information inherited, or copied, from the parent or source issue, and some information that's pre-configured as static data. Manually creating, setting up, and linking each of these issues, repeatedly, simply takes too much time.

The solution: define issue templates

With Elements Copy & Sync, you can define issue templates that can be reused as often as needed to create multiple issues at once, so you will never have to waste time creating the same issues over and over again.

Tutorial

This guide explains how to set up a recipe that will create three issues each time it is used based on a pre-configured template.
These three issues will have distinct values in their "Summary" and "Assignee" fields, but they will all inherit the "Priority" field of their source issue. Additionally, they will all be linked to their source issue.

In this example, we will trigger the recipe from an issue with the key SUP-1.

Prerequisites

A recipe called "Create 3 linked issues" 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 "Create 3 linked issues" in the Active Recipes list.

3 - Click on the Target step in the navigation menu.

4 - In the "Number of targets" section, click on the Create a static number of issues option.

5 - In the "Issues to create" section, click on the Add issue button to define how many issues will be created by the recipe each time it is triggered.
In this example, we will create 3 issues.

6 - Use the Set Type and Summary text fields to initialize the "Summary" field values of each issue as well as their issue types.
In this simple example, these issues will have three different issue types and they will be titled "First issue", "Second issue", and "Third issue". You can also use the Insert button in each field to inject the value of a field from the source issue to a given issue.

7 - In the "Monitoring section of the page, use the Create link to source issue option to automatically set up a link between each issue and the source issue.

In this example we are going to use the "is blocked by" link type.

8 - Click on the Content step in the navigation menu.

9 - In the "Fields" section, enable the Set and synchronize fields option.

10 - Use the Add target field option to add the "Assignee" and "Priority" fields to the Fields Mapping table.

At this point, each issue created will inherit the "Assignee" and "Priority" values from the source issue when they are created.
In this example, we want each "Assignee" to be distinct.

11 - On the "Assignee" row of the fields mapping table, click on the "..." button, then select the Set value for each issue option.

A new set of rows, specific to the "Assignee" field of each issue, is displayed in the table.

12 - Use the Set static value option in each of these rows to initialize the Assignee of each issue with a distinct value.

In our example, two different users will be assigned to the three issues.

13 - And that's it! Click on the Save button.

Result

With these steps, you have configured a recipe that can create three issues each time it is used. If you open any issue on your instance and trigger the recipe, three issues will be created with the defined "Summary" and "Assignee" fields. The "Priority" of these issues will be automatically inherited from the "Priority" of the source issue. 

You can also trigger this recipe with a workflow post-function to automatically create these issues each time the status of an issue changes, or use an Automation trigger to do the same thing.

•••

New to Elements Copy & Sync? 
If this tutorial has stirred your imagination, why not give it a try? 
• Try Elements Copy & Sync for free •