Hi there! 👋
I want to clone a "template" issue from within another project and move the cloned issue to this project upon a manually triggered operation within an Epic issue. The parent of the resulting issue should be set to the key of the Epic from within the automation was triggered.
Is there any clone issue action in automation in which you can set the key of the source issue, which is that existing template issue?
Thank you for your insights! 🙏
Hi @Ward Schwillens_ Schwillie 👋
If you're looking to clone a template issue from one Jira project to another, our app Deep Clone for Jira offers a powerful and flexible solution.
With Deep Clone, you can:
Deep Clone offers multiple options how you treat the Parent field when cloning your issues. Meaning, you can just clone all issues under your Epic (without the Epic itself) and choose to keep the original Parent.
Hi @Ward Schwillens_ Schwillie
If you're interested in Marketplace add-ons, I think Issue Templates for Jira (developed by the company I work for) could be useful.
It lets you create reusable issue templates and use them to create issues via manual triggers (buttons, post-functions, or automation).
With this app you can:
This is a link to Issue Templates Support Center , where you can find the app's demo, documentation and more info in one place
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ward Schwillens_ Schwillie ,
Using Jira Automation, you can create an automation like the following to clone a "template" issue from another project and clone it to the current project:
You can use smart values like {{triggerIssue.key}}
to dynamically set the Epic link.
If the answer helps, please accept the answer.
Best regards,
Murat Seven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.