Skip to main content
Skip table of contents

Clone and Move recipes

What is a "Clone and Move" recipe?

Elements Copy & Sync can be used in several ways to copy Jira issues. Depending on their needs, Jira admins may want to give more or less freedom to their end-users in regards to how the issues can be copied. Indeed, whereas classic recipes are meant to let Jira admins configure precisely their copy and synchronization options, "Clone and Move" recipes let users decide what they want to copy

When users trigger a "Clone and Move" recipe from a Jira issue, they can select what they need to retrieve from the original issue, and where they want the clone to be created :

If they need to use a different link type or clone the issue in a different project and with a different issue type, users have the ability to decide, just before the clone issue is created.

Recipe configuration

By default, these recipes are meant to replicate the "Clone" and "Move" options available natively in Jira and let users do them in one single action instead of two. However, admins have the ability to customize these recipes in order to make them even more useful : 

  • The Source tab allows admins to restrict on which issues a Clone and Move recipe is available. It is configured exactly as the Source settings of a regular Copy & Sync recipe.
  • The Target tab allows admins to restrict where an issue can be cloned. It is configured exactly as the Target settings of a regular recipe, except that the "Multiple issues creation" and "Monitoring" options are not available and it is not possible to select a "Project Picker" field as a target.
  • The Triggers tab allows admins to retrict which users can trigger the recipe. It is configured exactly as the Triggers settings of a regular recipe, except only the "Limit which users can trigger the recipe" option is available, and these recipes cannot be triggered by post-functions or in search results.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.