Move issue with links

john_monteith
Contributor
October 17, 2024

I created an automation rule to move a created issue from the project it was created in to another project based on this Atlassian recommendation:

https://support.atlassian.com/cloud-automation/docs/move-an-issue-to-another-project-using-automation/ 

Move issue rule capture.PNG

The documentation for above recommendation does state:

"While many of your existing field values will be retained, some items, such as attachments, will not be cloned with the issue"

This leads to my problem, if the created issue has linked issues, these links are not conveyed to the cloned issue.

All projects involved are company managed projects and this rule has "Multiple Projects" scope with all relevant projects listed.

Does anyone know of a fix/workaround to this problem?

2 answers

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 17, 2024

Hello @john_monteith 

You could do something like this:

Screenshot 2024-10-17 at 3.25.57 PM.png

The Link Issue action allows you to select only one link type. If you have different types of links for the issues you might want to do different branches for different types of links. 

john_monteith
Contributor
October 18, 2024

I do have to make multiple branches due to there not being a singular type of link that will always be used. But otherwise, with a little trial and error to determine the inward/outward nature of the links, this works great.

0 votes
Luka Hummel - codefortynine
Atlassian Partner
October 22, 2024

Hi @john_monteith

A helpful solution might be to check out our app Deep Clone for Jira. Deep Clone allows you to clone issues along with their links, attachments, and subtasks, which could solve your problem of losing links when moving issues between projects.

With Deep Clone, you can ensure all linked issues are cloned seamlessly, offering more flexibility than basic automation rules. You can also configure Deep Clone to delete the issues after cloning, imitating the native Jira 'move' function. You can read more on that here.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events