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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,573
Community Members
 
Community Events
185
Community Groups

Custom field not recognized in Jira automation "additional fields"

Edited

Hi there, 

I have a team-managed project.  On the epic, I have a custom field called "Design Reviewers".  When this field is changed, I want to update the custom field called "Reviewers" on any issue in that epic that is of issue type "design".

I can get all of the logic working, but when I try to update the field, it fails, saying that the field "Reviewers" does not exist.  Here is the JSON I am using:

{
"fields": {
"Reviewers": {{issue.epic.Discovery Reviewers.asJsonObjectArray("name")}} }
}

The error I get is 

"

additional fields contains invalid field(s) in 'update' or 'fields" section

Reviewers

"

 

Any idea?  The Reviewers field is on the issue, and other automation is referencing it.

1 answer

1 accepted

1 vote
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 19, 2022

Hi @Dave Vronay and welcome to the community,

To be honest this rule was a real pain in the ***. It took me a solid 30 mins to figure this out. The json that worked for me was the following:

{
"fields": {
"Reviewer": {{issue.epic.Design Reviewer.asJsonObjectArray("accountId")}}
}
}

Of course modify the above fields to your likings. The whole rule was like this (I choose the trigger to be issue updated for my tests):

community rule.png

Let me know if that works out for you!

This works, but - for some unknown reason - it does NOT work if the field is called "Reviewers".  It works with any other name...  

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 21, 2022

Whaaa??!?!?

You mean the plain reviewer or the design reviewer?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events