You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am trying to automate a people picker custom field that if used on the request form, allows a user to type in name or ID and resolves to the person.
We need to correct the field since we see 35% of them are incorrectly filled and we have a pure text field (custom) pulled from a system.
I believe the pulled text field is the "ID" for the people picker but at first trying to automate in JSON we get a casting error.
I tried to follow posts in the community but often the situation is different so here is the code I'm trying to use:
Note: 123456 is the people picker field; 654321 is the text field we've retrieved to update it...this is failing under: "Error while parsing additional fields. Not valid JSON."
{
"update" : {
"customfield_123456" : {{ issue.customfield_654321.asJsonStringArray }}
}
}
When I switch this to:
{
"fields" : {
"customfield_123456" : {{issue.customfield_654321.asJsonObject("key")}}
}
}
I no longer get an error in automation; the audit says "Success"; however the people picker field (customfield_123456) is still empty.
To be sure, the customfield_654321 does have a value in it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.