Bulk Copy #Elements Copy & Sync
Use case benefits
Create new projects with standardized issues as part of a consistent process
Streamline your process control by bulk cloning 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, Epics, 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, saving the user significant time.
Bulk clone, 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 clone, 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 cloned, cleared, or changed. This flexibility makes the cloning process smoother and more adaptable to each user’s context.
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 issue after a change in the Master project. This ensures that every user benefits from consistent documentation, whether they’re working on a new story or managing an Epic.
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, Epics, 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, saving the user significant time.
The Jira issue templates in your Master project may include fields you sometimes want to clone, 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 cloned, cleared, or changed. This flexibility makes the cloning process smoother and more adaptable to each user’s context.
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 issue after a change in the Master project. This ensures that every user benefits from consistent documentation, whether they’re working on a new story or managing an Epic.
Tutorial
Bulk clone 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. Cloning 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. The cloning feature is designed to scale, helping every user manage large projects without frustration.
Have questions about bulk cloning 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. This lets you add consistency across multiple teams and ensures smooth cloning operations.
More use cases
One app, 100+ use-cases
Discover more ways your team can use Elements Copy & Sync to standardize your processes.
