Can I use automation to change linked issues link type?

Question

My challange is this: in a Jira cloud project a number of tasks have been cloned. This results in each issue having a summary field prefixed with "CLONE" and an issue link of type "clones" which references the issue it was cloned from. I would like to create an automation rule that could convert the issue link type from "clones" to "related to".

I have successfully created a rule that for a single issue could do that; however, I dont't want to open all issues one after the other to apply the rule. I want to be able to apply a rule that will fix all issues in the same time. As nested branches are not supported I doubt it is possible. Any thoughts? Any hints to provide another approach? I have looked at little at python for jira which seems to support the looping mechanism needed but I would rather stay entirely inside Jira.

Marlene Kegel - codefortynine · Answer

Thank you for your feedback, @Frederik Vindum! I am happy to hear that you were able to solve your problem with help of the Atlassian Community :)

Frederik Vindum · Answer

Hi @Marlene Kegel - codefortynine

Thank you for getting back to me and pointing me in an interesting direction. Seems your product can help me. I'll be sure to check it out; however, I have moved on with reating my own Jira Automations.

/Frederik

Marlene Kegel - codefortynine · Answer

Hi @Frederik Vindum,

I'm Marlene from codefortynine.

If you are not able to find a suitable solution with Jira Automation, you could try our Marketplace app Deep Clone for Jira, which - I believe - covers your use case.

With Deep Clone you can

* Bulk Clone several issues at once
* Remove or change the prefix "CLONE-" while Bulk Cloning
* Change the "clones" issue link type to "relates to" while Bulk Cloning

You would simply have to

* Filter for the issues you want to bulk clone using the advanced issue search
* Click on the Bulk Clone button
* Uncheck "prefix summary" and configure "Add issue link between clone and original issue" under "advanced option" in the Deep Clone Bulk Clone cofiguration.