Jira Automation - cloning tasks and then assigning them to a trigger Epic

[Lena Babayev]

In our project, I have an epic set up with tasks that i want to replicate every time a similar epic is created. I have a rule that is triggered by an Epic that looks to the list of these tasks and clones them. My problem is that I can't get the new cloned issues to be associated to the trigger Epic. Since the trigger is the Epic, when I select the Fields to Set ... Epic Link --> "Copy from Trigger Issue" - I get the error 

No fields or field values to edit for issues (could be due to some field values not existing in a given project)

Not sure what else I am missing here. 

[Joseph Chung Yin · Accepted solution]

@Lena Babayev -

The problem with Set ... Epic Link --> "Copy from Trigger Issue", it is because the triggering issue is the Epic issue and there is no Epic Link field value.

When you create (clone) the tasks, you will need to set the Epic Link for those tasks with the Epic's issue key.

Can you provide a detailed screen shot of your automation rule, so we can review it further and suggest with a solution to resolve your ask.?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Lena Babayev]

Here is the clone action 

[Joseph Chung Yin]

@Lena Babayev -

Hi Lena:

Thanks for the update.  I just setup a test automation rule (similar to what you provided), and everything works just fine

You may want to remove your custodian field out from rule - essentially just setup your rule to clone the children of FEEDS-10089 Epic (simplify the rule to just copy the issue summary and add the Epic link relationship to the newly created Epic) to ensure the cloning works and roll-up works.  Afterward, adding additional fields to the rule and re test again.

Hope this helps.

Best, Joseph

[Lena Babayev]

I've removed all of the "Fields to set records" except the Epic Link Relationship but it still added the new tasks under the Feeds-10089 epic rather than under the trigger epic

Rule and audit log attached

I also thought and tried to run this by adding a subsequent step and creating the link after the issues were cloned, but there I can't make the issues "child" issues of the target Epic, but can only create a linked  relationship - sub task of target issue - which is not what I am looking to do.  :(

[Lena Babayev]

I read online some changes that are expected for child issues and that JIRA is moving more toward "linked issues" - I 'm hoping that I'm doing something wrong and NOT that the functionality is no longer going to be supported in this way. 

https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/#What-do-you-have-to-do

[Joseph Chung Yin]

@Lena Babayev -

In your Clone issue action, just set it up as follow -

You don't need to specify the project.  The reference link you provided has to deal with how issue is roll-up and should not impact the automation setup.

All the cloned issues should only be associated to the new Epic that was created and not re-establish the epic link back to the original Epic.  

Do you have any other automations which may somehow impacting this new automation rule?  Please check.

Best, Joseph

[Lena Babayev]

Wanted to come back here and provide the solution that finally worked: 

Epic Link value in the Clone Issue Seciton as {{triggerissue.key}}