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!
{
"update": {
"issuelinks": [
{
"add": {
"type": {
"name": "Cloners"
},
"outwardIssue": {
"key": "{{issue.key}}"
}
}
}
]
}
}
#jiracloud
#jirapremoim
#companymanaged
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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ah my bad. Please use the below setting
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the 'Copy to' custom field type? Are you sure for the not triggered issues, the value equals to COMEX?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.