Jira Automation Cloning Epic and its child is not working

[Yee Ming Chew]

Hello, 

I am currently using Jira Cloud. I tried the automation to clone epic solution provided here Clone Epic, Stories and Subtasks tree with Jira Au... - Atlassian Community.   but it is not cloning the. I have gone through multiple times to ensure I am following the solution correctly but only the Epic is cloned but not the child tasks.  Can anyone point out what's wrong with the automation rule I have setup?

[Bill Sheboy · Accepted solution]

Hi @Yee Ming Chew 

What type of project are you using: company-managed or team-managed?  You may find that information at the bottom-left side of the page's expand area.

And, would you please post an image of the audit log details showing the rule execution?  That may help to explain what you are observing.

Until we see those...

I suspect the problem is the branch.  And that could be replaced by a JQL branch with:

parent = {{triggerIssue.key}}

Kind regards,
Bill

[Yee Ming Chew]

@Bill Sheboy , The project type is company-managed.  Based on the Audit log, looks like the rule is not executed. 

[Bill Sheboy]

You have created a rule which is manually triggered. 

And so you must manually start the rule, selecting it from the issue view under the Actions menu at the top-right side.

[Tina Rusnak]

Hi Bill - I have had great success with cloning and automation however now with the Parent taking place of Epic Link I am having troubles. All amazing cloning is working EXCEPT the Stories are keeping the triggered Epic as the Parent not moving to the new cloned epic - I tried all the options - any ideas? Do we need to update the "epic key" to a parent key? thanks!

[Bill Sheboy]

Hi @Tina Rusnak -- Welcome to the Atlassian Community!

If you created / cloned the epic in the rule, did you save the key in a variable for later use in the parent field?

If you did that and it did not work, please create a new question, perhaps linking back to this one for context.  This is an older thread and creating a new one will ensure the maximum number of people see it to offer suggestions.

When you create your question, remember to include:

• what version of Jira you are using: Cloud, Server, or Data Center
• your project type: company-managed or team-managed, software or work management, etc.
• an image of the complete rule
• an image of any relevant actions / conditions / branches causing challenges
• an image of the audit log details showing the rule execution
• explain what is not working as expected, and why you believe that to be the case

Thanks!

Kind regards,
Bill

[Tina Rusnak]

Bill I did use the variable just put it in the wrong field - I was just going to let you know! It is working great! Cheers and thanks!

[Tina Rusnak]

@Bill Sheboy Hi! I just noticed this today; it seems after the successful cloning, on the trigger Epic, the child stories are still connected to the trigger Epic properly, but the drop-down option is no longer showing on the timeline view so you can't see the trigger epic child on the timeline any longer. Our goal is to NOT bring over the component fields at all from the Trigger Epic and all its children, subtasks. That is currently all working great.

We are on latest free Cloud version, company managed

Steps

1. Running Epic Clone to New Project

2. Coning success

3. Go back to Trigger Epic in timeline view

4. Note children are still connected, but not in the actual timeline view.

5. See Timeline image of the trigger Epic after cloning below

6. See Automation setup screen shots below

Thank you!

[Bill Sheboy]

Are you noting the new child issues of the epic are not linked to the correct one, or something else?

Perhaps if you post an image of the audit log details that will help explain it.

[Tina Rusnak]

All the new epics and their children and grandchildren are all good in the new project; it's the originating project that is having some change unexpectedly.

For some reason, after the automation is complete, on the trigger Epic, all the children are still technically and visibly connected, we did not lose anything EXCEPT

on the literal timeline view, you can no longer click on the arrow to expand the epic view the kids on the timeline/roadmap. The arrow is gone.

The logs are gone, I need to another test.

The work around seems to be - do a bulk update to re-associate all the children with the epic then the timeline works again.

[Bill Sheboy]

That is curious: if your rule is not editing the issues I would not expect their linkages to the parent Epic to change. 

You may want to work with your Jira Site Admin to create a support ticket to ask Atlassian about this symptom: https://support.atlassian.com/contact/#/

[Tina Rusnak]

Yep will do it is super odd. Thank you!

[Yee Ming Chew]

It works. Thank you so much @Bill Sheboy . Appreciate it!