How to update multiple objects using Jira automation (Edit Assets field attributes)
Asked by Nicole:

I have an asset custom field (Contact (IF)) which can contain multiple values (Asset Objects).

![Screenshot 2023-10-03 at 15.33.00.png](/t5/image/serverpage/image-id/284216i1E0F98421B9BBC59/image-size/large?v=v2&px=999 "Screenshot 2023-10-03 at 15.33.00.png")

I am trying to create a Jira automation rule to update the share_coverage attribute on each object using the existing values and adding new values, respectively.   
![Screenshot 2023-10-03 at 15.33.44.png](/t5/image/serverpage/image-id/284220iEC9D009717901D66/image-size/large?v=v2&px=999 "Screenshot 2023-10-03 at 15.33.44.png")  

The automation:  

![Screenshot 2023-10-03 at 15.34.25.png](/t5/image/serverpage/image-id/284221i0F96EF5959EF5601/image-size/large?v=v2&px=999 "Screenshot 2023-10-03 at 15.34.25.png")  

Currently, it is concatenating all the existing attributes and updating each object with the old concatenated values as well as the new values.   

![Screenshot 2023-10-03 at 15.35.05.png](/t5/image/serverpage/image-id/284222i55752526E3F3C166/image-size/large?v=v2&px=999 "Screenshot 2023-10-03 at 15.35.05.png")  

Instead of just adding REM to each object respectively.

Does someone perhaps know if there is a solution for this in Jira automation?


Answers:
author: Bill Sheboy
body: Hi [@Nicole](/t5/user/viewprofilepage/user-id/5331641) -- Welcome to the Atlassian Community!

Would you please show you entire automation rule, including the details of the edit assets action? That may help explain what you are observing.

Kind regards,  
Bill


author: Nicole
body: Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

Apologies. We did not manage to resolve the issue and ended up not needing it at the end of the day. I will mark the Question as answered.

Thanks :)


author: Nicole
body: ![Screenshot 2023-10-04 at 10.51.11.png](https://community.atlassian.com/t5/image/serverpage/image-id/284366i9C303771D89C115F/image-size/large?v=v2&px=999 "Screenshot 2023-10-04 at 10.51.11.png")![Screenshot 2023-10-04 at 10.51.26.png](https://community.atlassian.com/t5/image/serverpage/image-id/284367i91423DA9D7CDFB6C/image-size/large?v=v2&px=999 "Screenshot 2023-10-04 at 10.51.26.png")![Screenshot 2023-10-04 at 10.51.32.png](https://community.atlassian.com/t5/image/serverpage/image-id/284368iDE61753A04D0C4D4/image-size/large?v=v2&px=999 "Screenshot 2023-10-04 at 10.51.32.png")  

Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

Thank you for your response. Please see attached as requested.

Basically, the Contact (IF) custom field relates to the Contact Object Type and the Instrument (IF) custom field relates to the Share_Coverage attribute within the Contact Object.

The issue seems to be that the automation cannot determine when the Contact (IF) field has more than one value and deal with them separately.

Best,

Nicole

comments: author: Bill Sheboy
body: Hi, Nicole.

Would you please clarify which of your custom field id values are for which field? That will help me understand what the branch and variable are accessing. Thanks!

I believe you would need to confirm your last idea about "cannot determine when the Contact (IF) field has more than one value" using writes to the audit log. Do you mean in the advanced branch or in the create variable action?

Generally, when a smart value, list has one value it may be handled as if it was a single field or a list. When it has multiple, it is a list.


author: Bill Sheboy
body: Hi [@Nicole](/t5/user/viewprofilepage/user-id/5331641)

Just following up to check if your question was resolved. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes.

Thanks!


Tags: cloud