Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How to update multiple objects using Jira automation (Edit Assets field attributes)

Edited

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

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

The automation:

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

Instead of just adding REM to each object respectively. 

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

3 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 03, 2023

Hi @Nicole -- 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

Hi @Bill Sheboy 

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 :)

Screenshot 2023-10-04 at 10.51.11.pngScreenshot 2023-10-04 at 10.51.26.pngScreenshot 2023-10-04 at 10.51.32.png

Hi @Bill Sheboy 

 

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

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 04, 2023

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.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 04, 2023

Hi @Nicole 

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!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events