nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cloning Epics including stories - Jira Automation

Kurt Smith_3hs3w5

I found a solution that is working for some folks but not for me. Any suggestions? I'm using Jira Cloud.

This clones everything that is linked directly to the epic. You could define the same rule-logic for the story-subtask relation ship.

Details of "Clone" Block:

If you are using Jira Premium you can also use "portfolioChildIssuesOf" to gather the tickets inside the epic which would also fetch sub-tasks.

However now you need to pay attention that your Automation does not try to link cloned subtasks to the new epic.

Accepted answers

Marc_b3d8aj

This works for me:

1. Run when issue linked via "Cloners"

2. Condition: only if the issue type is Epic AND it's linked "is cloned by" - meaning the issue you just cloned

3. Scriptrunner query to get the issues in the Epic linked to the Epic that was just cloned

issuefunction in issuesinepics("issuefunction in linkedissuesof(\"key = {{triggerissue}}\",\"clones\")")

4. Clone issues in Epic and set the Epic Link to the Trigger issue

5. Delete the issue link "clones"

Screen Shot 2022-10-13 at 4.16.25 PM.png Screen Shot 2022-10-13 at 4.19.31 PM.png

All comments

Trudy P Claspill

How is the solution not working for you? What problem are you encountering?

Kurt Smith_3hs3w5

It simply doesn't work....the Epic clones but no stories.

Trudy P Claspill

Can you provide a link to the post where you got this suggestion?

I think the problem is in the branch "For JQL" where it says

"Epic Link" = {{destinationissue}}

Reviewing the information for the trigger I understand it to be saying that "issue" would be the source issue (the Epic you are cloning) and "destinationissue" would be the resulting Epic generated by the clone action. So, if you want to clone all the child issues in the source Epic then I think the branch should be

"Epic Link" = {{issue}}

I haven't tested this Automation myself, so this is just based on a desk check.

Kurt Smith_3hs3w5

Here is the original link:

Cloning Epics including stories - Jira Automation (atlassian.com)

Here is the audit log from the automation - MT-30 is the Epic being cloned and MT-48 is the clone:

Action details:
Issue linked
Destination issue (to perform actions on this issue use a 'Related branch', you can also access it via {{destinationIssue}}):
MT-30
Source issue (the main branch of the rule will execute for this issue and you can access it via {{issue}}):
MT-48
JQL condition
The following issues did not match the condition:
MT-48
This may be due to any of the following reasons:
the issue didn't match the specified JQL (most likely)
the chosen rule actor doesn't have permissions (or issue security level permissions) to view the issue
the issue was deleted or wasn't indexed by Jira yet (in rare circumstances)
We recommend using the 'Issue fields condition' for more consistent results.

Marc_b3d8aj

This works for me:

1. Run when issue linked via "Cloners"

2. Condition: only if the issue type is Epic AND it's linked "is cloned by" - meaning the issue you just cloned

3. Scriptrunner query to get the issues in the Epic linked to the Epic that was just cloned

issuefunction in issuesinepics("issuefunction in linkedissuesof(\"key = {{triggerissue}}\",\"clones\")")

4. Clone issues in Epic and set the Epic Link to the Trigger issue

5. Delete the issue link "clones"

Screen Shot 2022-10-13 at 4.16.25 PM.png Screen Shot 2022-10-13 at 4.19.31 PM.png

Trudy P Claspill

Hello @Marc

"issueFunction" is not native to Jira JQL. Your solution requires a third party app. Are you using Adaptavist Scriptrunner?

Marc_b3d8aj

Yes, Scriptrunner is required in order to use that JQL function.

Taranjeet Singh

@Kurt Smith Just after spot checking your original rule (which seems to be similar to the rule that @Trudy P Claspill suggested), I think that your rule is not working, maybe due to a typo error in your "Related Issues" JQL query in the smart value {{destinationissue}}. It should be {{destinationIssue}} instead. Give it a try and see if this fixes your rule.

I hope it helps!

Melissa Lato

For all those who do not want to buy a tool this has been answered via this link Clone-EPIC-amp-Stories-to-New-Epic-and-link-New-Stories

Luka Hummel - codefortynine

Hi, I'm Luka from codefortynine 👋

While it is possible to clone hierarchies with Jira Automation, this can be quite finicky and can break easily if project or issue configurations change.

If you are open to use a third-party app, our Deep Clone for Jira can clone whole issue hierarchies, including Initiatives, Epics, Tasks/Stories, and Subtasks.

Deep Clone for Jira_Epic Tree Clone.gif

Navigate to the issue you want to clone
Click Action menu ••• > Deep Clone
Select Epic/Tree Clone
Configure and create your Epic/Tree Clone

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland