Menu
Bulk Copy #Elements Copy & Sync

Leverage a template project in Jira by bulk copying issues with Elements Copy & Sync

Use case benefits

Create new projects with standardized issues as part of a consistent process

 Streamline your process control by bulk copying Jira issue templates

Set up templated deliverables in Jira and easily add them to new projects with Elements Copy & Sync. When your processes repeat often, you can create template issues like Initiatives, Epic, stories, or tasks in a Master or template project, then clone everything into a new project from Jira search results. Even the attachments and comments can be copied.

Copy, clear, or change field values based on the target project

The Jira issue templates in your Master project may include fields you sometimes want to copy, other times clear, or even set with static options. To reduce the manual work when filling a new project, Elements Copy & Sync no code field mapping options allows you to decide with each recipe which fields will be copied, cleared, or changed.

Synchronize changes between Master project issues and cloned issues

Have you updated the detailed process to follow in the description of a template issue, perhaps diagrammed in an attachment? Or changed a component or label? By activating synchronization from source to target in the recipe, there is no need to manually update each cloned issues after a change in the Master project.
Set up templated deliverables in Jira and easily add them to new projects with Elements Copy & Sync. When your processes repeat often, you can create template issues like Initiatives, Epic, stories, or tasks in a Master or template project, then clone everything into a new project from Jira search results. Even the attachments and comments can be copied.
The Jira issue templates in your Master project may include fields you sometimes want to copy, other times clear, or even set with static options. To reduce the manual work when filling a new project, Elements Copy & Sync no code field mapping options allows you to decide with each recipe which fields will be copied, cleared, or changed.
Have you updated the detailed process to follow in the description of a template issue, perhaps diagrammed in an attachment? Or changed a component or label? By activating synchronization from source to target in the recipe, there is no need to manually update each cloned issues after a change in the Master project.

Tutorial

Bulk copy up to 1000 Jira issues at once

As a Process Manager, you use Jira to store and reuse a “library project” which contains hundreds of issues. Copying hundreds of issues manually is not a satisfying solution. Thanks to Elements Copy & Sync, it is possible to duplicate all these issues at once based on a Jira search result or a Jira Filter.
Copy & Sync Product Manager: Thibaut

Have questions about bulk copying Jira issues?

FAQ

Can I clone a project?

You can clone all the issues in a project either from the Search or filter screen, or alternatively use Automation to copy issues when you create a new project.

Does this bulk clone Epics?

 Yes, you can bulk clone Epics and all the issues under the Epics.

How do I choose the project where the issues will be bulk copied?

You can configure the target projects in the recipe. If you add multiple projects, the user will then be able to select the project where they want to copy the issues.
More use cases

One app, 100+ use-cases

Discover more ways your team can use Elements Copy & Sync to standardize your processes.

Escalate issues to teams in different Jira projects

Clone and move Jira issues easily between Jira Service Management Agents and development teams

Create multiple issues dynamically for employee onboarding

Simplify the work of HR teams using Jira by creating all tasks linked to a new employee onboarding

Create multiple subtasks for software testing

Automatically create multiple testing issues in Jira thanks to a set of templated subtasks