No tokens. No web requests. Just add a recipe to your rule.
Elements Copy & Sync is the Jira Cloud app dedicated to cloning and synchronizing work items, with their fields, comments, attachments and child items, across projects and even across Jira instances.
If you've ever tried to run an Elements Copy & Sync recipe from Jira Automation, you know it took a bit of work. You needed an API token, an actor set up in Copy & Sync, and a "Send web request" step with a URL copied from the recipe's Triggers tab.
Because Elements Copy & Sync didn't appear in the Automation action catalog, plenty of teams never knew the integration existed.
That changes today.
What's new: a native "Run a recipe" action
Elements Copy & Sync now appears directly in Jira Automation, next to the actions you already use:
Actions → Other apps → "Elements Copy & Sync – Run a recipe".
An admin connects Elements Copy & Sync to Automation once. After that, adding a recipe to a rule takes three choices in a simple dialog:
- Source: the current work item by default. You can also use a fixed work item key or a smart value, such as
{{issue.parent.key}}. - Recipe: pick one from a dropdown of your active recipes. What gets copied or synced stays defined in the recipe.
- Target project and work type: taken from the recipe, or chosen from a dropdown if the recipe has several targets. Smart values can make it dynamic too by adding a conditional logic.
It works with local classic recipes and remote recipes, and with any trigger: work item created or transitioned, manual, or scheduled with JQL. One rule can also run several Copy & Sync actions in a row.
Learn more on how to use the new Automation action
What you can build with it
Elements Copy & Sync adds cross-project and cross-instance copying and syncing to the rules you already build. A few examples:
- Project managers: when an epic moves to "Ready for dev", copy it and its child work items to the delivery project automatically, with no manual steps.
- Support managers: when a JSM request is escalated, create the linked bug in the dev project and keep both in sync, from a single rule.
- Project templates: when a new client or project kicks off, copy a template epic with all its standard tasks and subtasks into the right project, so every team starts from the same structure.
Lighter rules, fewer steps, lower Automation costs
Atlassian Automation is moving to usage-based pricing: every trigger, condition, action, branch and loop that runs now counts as a step, and extra usage billing starts on December 3, 2026. Many admins are now looking at how to keep their rules lean.
This is where the app helps. Copying a work item with its child items, comments, attachments and links usually takes several branches and actions in a rule, or even several rules. With Elements Copy & Sync, everything is defined once in the recipe, and the rule simply calls it in one action. Ongoing synchronization between the copies is then handled by Elements Copy & Sync, so you don't need extra rules trigerring for every update.
The result: shorter rules that are easier to read, easier to maintain, and lighter on your Automation usage.
Built for admins who want control
- Clear accountability: recipes run as the current user or the Automation rule actor. No API token or actor to manage in Elements Copy & Sync settings.
- Choose what's available: in each recipe, go to Triggers → Recipe availability → "Jira Automation actions". It's on by default, and you can turn it off for any recipe.
- Full audit trail: every run appears in Elements Copy & Sync Activity Logs with a new "Automation" trigger type. Errors show in both the Elements Copy & Sync log and the Automation audit log.
- Nothing breaks: your existing "Send web request" rules keep working as before.
Get started
Open Jira Automation, add an action, and look for Elements Copy & Sync – Run a recipe under Other apps. Our step-by-step guide walks you through the setup: How to trigger recipes with Automation.
Not using the app yet? Try the app for free.
How will you use it? Share your use cases or questions in the comments, we'd love to hear from you.
