Elements Copy & Sync

Easily clone and sync Jira issues across projects or instances

Automatically clone and sync Jira work items and spaces

Keep teams aligned with flexible copy and synchronization recipes. Streamline key workflows like issue escalation, project cloning or epic copy.

discover how to clone jira issues with elements copy & sync

Easily clone work items and spaces in Jira

Stop wasting time on manual cloning: automatically clone Jira issues and spaces with Automation or post-functions.

Clone entire hierarchy of issues and copy their attachments, comments, labels, custom fields and more.

Copy & synchronize work items between different spaces and instances.

Seamless Jira work item syncing across spaces

Improve cross-team collaboration by syncing cloned issues to keep teams aligned and up to date.
Define which fields should be synchronized and how (one way or bi-directional sync).

Use Elements Copy and Sync to seamlessly sync Jira work item across spaces
Discover how to go further Jira native cloning features with Elements Copy & Sync

Go further Jira native cloning features

Design custom copy and sync recipes and trigger them automatically in a few clicks:

•Manually

•Through automation

•Using post-functions

Pick which work item field should be copied and/or synchronized, and configure your recipe.

Why teams clone and sync Jira issues

Clone, sync and automate work items across Jira without losing context or wasting time on copy-paste.

Bulk clone issues, clone epics and entire projects

Native Jira clones one work item at a time. Clone thousands at once, keep epic hierarchies intact, or duplicate entire projects.

Clone and sync across Jira instances

Clone and sync between separate Jira and JSM sites.

Clone Jira issues with full context

Pick the fields, comments, and attachments to clone or sync, and map select values between fields, even when teams use different options.

One- or two-way Jira issue sync

Keep work items aligned across spaces and teams. Changes to fields, comments, and statuses sync automatically, in one direction or both.

Automate cloning & subtask creation

Run recipes manually, through Jira Automation or post-functions, with no code, from one reusable, centralized recipe.

Enterprise-grade security

SOC 2 Type II, ISO 27001 and data residency options.

How Jira teams use Elements Copy & Sync

Explore how teams clone, sync and escalate work across Jira projects and instances, without manual copy-paste.

  • Elements Copy & Sync is a great app and saves us a lot of money

    We sync issues between JSM and Jira Software. In this case we don’t need the expensive JSM agent licenses for all our employees. The support is also great, fast and good. Just what a customer need.

    Yorick Dijk,Service Manager, EDSN
  • This app is incredibly useful for us!

    I like that it is not overloaded or overcomplicated. It simply does what its name suggests by letting you define rules that COPY and SYNC Jira issues as you want. It’s very easy to configure, too. We have been using it for a couple of years and created over 25.000 work items effortlessly with the help of Elements Copy & Sync.

    Jann Boumann from AMAGOO

Frequently asked questions

Couldn’t find what you need?

  • Recipes to copy or synchronize issues can be triggered manually, on transition by adding them to a post-function, or by using the public REST API with Automation for Jira. Learn more about all the ways to trigger Elements Copy & Sync on the documentation.

  • Yes, you can clone Epics or all the issues in a project with Elements Copy & Sync. You can copy these issues either in bulk from the Search or Filter view, or individually (for an Epic) or using Automation for all the issues in a project. Follow this tutorial for how to clone an Epic, or watch this video on bulk cloning.

  • Elements Copy & Sync is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA). With JCMA you can:
    Automatically migrate most of your Operations, Synchronizations, and Fields Mapping.
    Cloud-side, these become Elements Copy & Sync recipes with mappings embedded in each recipe.
    Key points:
    JCMA will adapt your configuration “as close as possible” to Cloud concepts.
    After migration, you should review and adjust recipes in Cloud to match your exact needs.
    Certain features (Data Panels, Copy to Confluence, Copy to remote instance with old link model, Velocity) are not or not fully migrated and need manual handling.
    More info about your migration from Data Center to Cloud

  • You can copy fields, Forms, checklists, comments, attachments, and even statuses with Elements Copy & Sync. See the full list of content that can be copied on our documentation.

Let’s make Atlassian
work better for your team

Our apps connect Confluence, Jira and Bitbucket with the tools you already use, like Git, Microsoft 365 and SharePoint.
Tell us what you need and we’ll help you find the right solution.