Auto clone issue but use relates to link type instead of Clones

BenWade May 8, 2024

Hi everyone,

I have an automation rule that clones issues based on a custom field. It creates clones with the "Clones" issuelink type.

I need another automation that will also clone the issue and will create "relates to" link types. However, I cannot use the "Cloners" link type as another automation rule is linked to it. So, basically, the title of this post explains what's needed.

Here is the code used to link cloned issues. I believe I simply need to modify the code below to use the "relates to" link type instead of "Cloners". However, I'm unsure if this is correct and how to properly modify the code. Can someone help me with this?

If only the code below needs to be modified, please provide adjusted code for my case. Thank you!

image.png

image.png

{
"update": {
"issuelinks": [
{
"add": {
"type": {
"name": "Cloners"
},
"outwardIssue": {
"key": "{{issue.key}}"
}
}
}
]
}
}

 

#jiracloud
#jirapremoim
#companymanaged

2 answers

1 accepted

3 votes
Answer accepted
Fazila Ashraf
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 8, 2024

Hi @BenWade 

Is there a reason why you do not want to handle it link below? Basically to remove the clone link and relink with a different type with additional blocks?

Screenshot 2024-05-08 at 11.55.22.png

BenWade May 8, 2024

I have another automation in place. If the status of the issue in Project A has changed, then the status of the issue with issuetype link 'Clones' in another project will be changed as well. To avoid disruption, I need to use the 'relates to' issuetype link

BenWade May 8, 2024

i guess your solution can work. I just need to use 'Link issue to' step instead of JSON, right?

BenWade May 8, 2024

image.png
So this is the flow but it does not link the issues. What can be the problem?

Fazila Ashraf
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 8, 2024

ah my bad. Please use the below setting

Screenshot 2024-05-08 at 12.55.39.png

Like BenWade likes this
BenWade May 8, 2024

I will chnage it now. But why 'trigger issue' does not work? It should work, no? Because the ticket in Porject A triggers the automation when I add value to 'Copy to' field
image.png 

Fazila Ashraf
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 8, 2024

What is the 'Copy to' custom field type? Are you sure for the not triggered issues, the value equals to COMEX?

0 votes
Luka Hummel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 22, 2024

Hi @BenWade

If you are willing to use a third-party app, our app Deep Clone for Jira could help you with your goal. Deep Clone can be configured to create any issue link type between source and cloned issue. You can also integrate Deep Clone in your Jira Automation with a looping transition.

Suggest an answer

Log in or Sign up to answer