Team field is not copied when splitting issue
Asked by AB:

It seems like a known issue but I see a few workarounds already shared by community members. I have tried using Automation but unable to achieve the desired results. here are some screenshots for reference;![1.png](https://community.atlassian.com/t5/image/serverpage/image-id/346729i98739F1DCD6F2FCA/image-size/large?v=v2&px=999 "1.png")![2.png](https://community.atlassian.com/t5/image/serverpage/image-id/346728iDD6C0018F7DD6D07/image-size/large?v=v2&px=999 "2.png")![3.png](https://community.atlassian.com/t5/image/serverpage/image-id/346727i1004C48D4A9CDEED/image-size/large?v=v2&px=999 "3.png")


Answers:
author: Marc - Devoteam
body: Hi [@AB](/t5/user/viewprofilepage/user-id/5183787)

I think its a combination of the smart value and the rule.

[@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) is right on the smart value, but triggering on linking and then add the linked issue requires a brand.

If you don't branch all actions are on the issue that is triggering the rule, not the linked issue.

Try: (adjust to your link requirement and naming)

![Screenshot 2024-09-11 at 09.14.15.png](https://community.atlassian.com/t5/image/serverpage/image-id/346749i0DDDC272559C1621/image-size/large?v=v2&px=999 "Screenshot 2024-09-11 at 09.14.15.png")


author: Dick
body: Hi AB and Trudy,

The culprit of the automation is the left hand side of the equation: it should hold the name of the field (in this case being **Team** ). The righthand side of the original equation of AB is right, there is no need to put **.Id** in the smartvalue.

comments: author: Trudy Claspill
body: An acceptable alternative to using the field name is to use the custom field ID in the JSON code.

And it seems that the **id** attribute is required since using that eliminated the error received when it was not used.


author: Trudy Claspill
body: Hello [@AB](/t5/user/viewprofilepage/user-id/5183787)

Try using the value {{triggerIssue.fields.customfield_29790.id}}

comments: author: AB
body: Thank you for responding. It didnt work

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/346733i3B7331010E5CDC28/image-size/large?v=v2&px=999 "image.png")![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/346735i5A91FED45598CC34/image-size/large?v=v2&px=999 "image.png")


author: Trudy Claspill
body: Hello [@AB](/t5/user/viewprofilepage/user-id/5183787)

Which issue did you expect to be updated?

The way the rule is written the issue that is triggering the rule is also the one that is getting updated, and it is being updated with the value that it already has in that same field. I don't think that is what you want.

Which is the issue that was split? Which is the issue that was generated by the split?

When you look at the issue that was split and look in the linked issues section what is the link text (i.e. "split from" or "split to") that is shown to describe the link to the newly created issue?

The Issue Linked trigger is a unique trigger because there are two issues involved in the process, but only one of those issues can be considered the issue that triggered the rule. Depending on the type of link used and what the relationship is to the other issue, the issue from which the link is created may not be the one that triggers the rule.

For a more detailed explanation refer to the answer that I posted on this Question:

<https://community.atlassian.com/t5/Jira-questions/How-can-I-get-field-from-linked-issue/qaq-p/2807497#U2807518>

I suspect that the issue being split in your scenario is the one that is triggering the rule, and subsequently the one that the rule is trying to update.

To solve the problem you need to add a branch to change the focus to the issue created by the split. You can use the branch For: Related Issues: Destination Issue, and then nest the Edit action within the branch, as I have shown in my answer on the other post.


Tags: automation

data-center

jira-data-center