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
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.