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; } } }

Move issue with links

john.monteith

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?

Accepted answers

Trudy P Claspill

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.

All comments

Trudy P Claspill

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

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.

Luka Hummel - codefortynine

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.

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