Hi all,
I have created an automation to clone an epic and all underlying issues from a template. Stories below the epic are linked to each other. (“is required by” / “requires”) Is it possible to clone the linking as well? I already tried it in a new Branch but it doesn´t work.
Example: Story 1 is required by Story 2 --> Clone Story 2 is required by Clone Story 2
Thanks in advance for your answers.
Hi @mrmi Müller Michael and welcome to the community!
Jira Automation’s built-in Clone issue action unfortunately copies only the target issue itself – it does not replicate the issue links that connect template stories to one another, so the relationships are lost in the newly created Epic.
If you would like those “is required by / requires” links (or any other link type) to be carried over automatically, take a look at our app Deep Clone for Jira.
To do that, you just need to configure the Issue links option under Clone additional fields when configuring your Epic Clone.
On cloning the issue links are not cloned, this is also not an option in automation.
The API has no clone endpoint, so this route can't be taken.
Why is this not there, this is due to you might have not got enough rights to the issue linked on the issue you are cloning.
You can explore 3rd party apps from the marketplace.
https://marketplace.atlassian.com/search?hosting=cloud&query=clone
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.