You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I want to clone a task to a specific epic under a different project (bare minimum) and if possible also mirror the activity on that task regardless of which project I'm working from.
Hi Helen - Welcome to the Atlassian Community!
Yes, you can create an automation rule that will Clone the issue into a separate project and use a specific Epic for the newly created issue. Is that what you are wanting to do?
Yes! @John Funk how would I go about setting that up? i know Luka below shared it but wiht deep clone. a) how do i do it without that b) if i do it with deep clone it only has 10 users. does that mean i can only give access to the projects to 10 people? sorry clearly a newbie ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let's start with what would trigger the creation of the clone. Would you be transitioning the issue to another status and that should cause the clone to get created? Or are you updating a field on the issue? Or something else?
And how will it know which Epic to make as the parent of the new issue? Will you hardcode that Epic key in the Epic Link field? Or will you want to get it in another manner?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @helen.maijub
Welcome to the Atlassian community.
You could potentially accomplish this through use of an automation rule. However it would have to be a multi-project/Global rule, and those can be created only by a Jira Administrator.
If the destination project/epic might vary, you would need a field in the source issue where you could enter the destination Epic.
Then you would trigger the automation rule on the source issue manually.
The automation rule would be able to clone the issue to the destination Epic.
To mirror activities from one issue to the other you would need 1..n separate rules depending on exactly what activities you wanted to mirror.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @helen.maijub and welcome!
Directly cloning to another project/epic is not possible by default. A simple solution is to clone the task first, then move it to a different project and assign the epic.
If you don't want to do this manually or if you want to clone many tasks at once, I can recommend Deep Clone for Jira, which supports your requirement.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you much! That's good to know. At bare minimum, if i wanted to clone to a different project under a specific epic. Is that possible? If so, are you able to share how?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@helen.maijub As @John Funk and @Trudy Claspill of course correctly pointed out, you can probably achieve your goal with an automation rule as well. Please see their responses above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michel Neeser Thank you very much for recommending Deep Clone for Jira.
@helen.maijub Welcome to the community! You can indeed use Deep Clone for Jira to clone issues under a specific epic by using the Clone and Edit feature to set the Epic Link field when cloning the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.