Jira automation: Linked Issues - Variable works in one clone and does not work in another
Asked by Cl?udia Silva:

Hi,

After starting with the trigger for the existence of an update in a certain field of an issue, there is a clone of that same issue and I create a variable to have access to its {{createdIssue.key}} which I named {{cloneParent}} .  
Then I want the linked issues of both the "Requirement" type and the "Functional Area" type to be cloned and the linked issue of the "is tested in" type to be the issue that I cloned previously and therefore I put the variable {{cloneParent}} . The issue is that for the "Functional Area" type it works perfectly but for the "Requirement" the issue is cloned but the linked issue does not appear.. And the process is exactly the same..  
Is there any explanation as to why it works in one and not in the other?

![screencapture-peekmed-atlassian-net-jira-settings-automation-2024-05-24-12_21_11.png](https://community.atlassian.com/t5/image/serverpage/image-id/325831i99CB83F98DCD3E3F/image-size/large?v=v2&px=999 "screencapture-peekmed-atlassian-net-jira-settings-automation-2024-05-24-12_21_11.png")![variable .png](https://community.atlassian.com/t5/image/serverpage/image-id/325832i5A4D8E569A6E58F3/image-size/large?v=v2&px=999 "variable .png")

Thank you !!


Answers:
author: John Funk
body: Hi Cl?udia

What is the difference between the two issues? Are they in different projects? Different Issue Types? Other things?

comments: author: Cl?udia Silva
body: Hi John,

First of all, thank you very much for the brief response. They are from the same project, the only difference is the type of issue, where one is of the "Requirement" type and the other is of the "Functional Area" type. However the issue type "Requirement" is an epic.. ![Is tested in.png](https://community.atlassian.com/t5/image/serverpage/image-id/325844i3E797B84A03739E9/image-size/large?v=v2&px=999 "Is tested in.png")

![Functional Area.png](https://community.atlassian.com/t5/image/serverpage/image-id/325846iE81D815016B9CEEA/image-size/large?v=v2&px=999 "Functional Area.png")![Requirement.png](https://community.atlassian.com/t5/image/serverpage/image-id/325845iF221FA9EDAB1FE98/image-size/large?v=v2&px=999 "Requirement.png")

Still, these two tasks are "is tested in" in the main issue and now that I cloned the main issue I wanted the two cloned tasks to appear in "is tested in". With the "Functional Area" type task I didn't have any problems but with the "Requirement" nothing happens. However, if instead of putting the variable in "is tested in" and just saying "Copy linked issues from current issue" both the cloned and the main variable are in "is tested in". My question is as I don't want to keep the original in "is tested in" I was trying to put the url of the cloned issue..


author: Cl?udia Silva
body: If you need any more information, please let me know. Thank you !!


author: John Funk
body: Sorry for the very late response. I am not completely following what you are doing. Maybe you write it line for line what is happening. Something like:

Issue A has a value changed.

Then Issue A is Cloned to Issue B,

Then I want to link Issue B to Issue A.

Something like that.


author: Cl?udia Silva
body: Hello, I still have the same problem. Can anyone help me?

Thank you!!


Tags: cloud

jira-service-management

jira-service-management-cloud