JMWE Cloud – need help cloning an Epic and all its children

[Ahmed Saci]

Hi everyone,

I’m trying to build a “Clone Epic” transition (workflow on the Epic issue type, Jira Cloud) that should:

1-Duplicate the Epic in the same project (summary prefixed with CLONE –),

2-Duplicate every child Story/Task (several custom issue-types) that currently belongs to that Epic,

3-Copy all custom fields, attachments, components, assignee, etc. from each original Story to its clone,

Link every cloned Story back to the new Epic (Epic Link / Parent),

I’m using JMWE Cloud

My current setup:(not work "not clone child issues")

Order Post-function Main settings
1 Create issue(s) – clones the Epic
• Project = Same as current issue
• Issue type = Same
• Summary = CLONE – {{ issue.summary }}
→ JMWE stores the key in jmwe.last.issue.created
2 Set Entity Property value on the original Epic
• Property name = newEpicKey
• Value = `{{ issue issueProperty('jmwe.last.issue.created') }}`
3 Sequence of Post-functions – supposed to loop over children
• Target issues = I tried both
 a) Child issues of the current issue in the hierarchy
 b) Issues returned by JQL → "Epic Link" = {{ context.currentIssue.key }}
3.1 inside the Sequence → Create issue(s)
• Project = Same as current issue
• Issue type = Calculated, template: {{ issue.fields.issuetype.id }}
• Epic Link (or Parent) = `{{ context.currentIssue issueProperty('newEpicKey') }}`
• Copy fields = All fields

[Paweł Mazur]

Hi @Ahmed Saci,

I'm Paweł, a Customer Success Manager here at Appfire. We’re the team behind JMWE 😊 I'm happy to help you out!

Here’s something we suggest trying:

1. Add the steps from points 1 and 2 as post-functions in a JMWE Sequence of Post-functions.
2. In step 3 of that sequence, set the Target issues to “Issues that belong to the current issue (Epic)”.
3. For the same post-function in step 3, we recommend adding a delay of about 7 seconds to ensure smooth operation.

If that doesn’t work, feel free to contact us through our support portal here -> Appfire Support Portal. We’d be happy to review your configuration and help you troubleshoot directly.

Cheers,
Paweł Mazur
Customer Success Manager, Appfire

[Luka Hummel - codefortynine]

Hi @Ahmed Saci

If you want your “Clone Epic” workflow transition to duplicate the Epic and every child Story / Task exactly as you described, you can make this happen with our app Deep Clone for Jira and its integrated Epic/Tree Clone post function.

[Ahmed Saci]

@Luka Hummel - codefortynine Thank you for your suggestion, but we are looking for a solution using JMWE, as mentioned in the title of my post