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.
Hi All,
I am trying to understand the automation experience differences on multi-choices and labels. The experience on labels is really good - you can add or remove a single label without touching the remaining ones. But with multi-choice, you have to set the full value.
Am I missing something? If this is the case, any suggestion how to achieve it with smart values?
Thank you,
Zekai
You can use the advanced option to add/remove data from a multi-select field. For example here is the JSON I use in one of my automations that removes the user that triggers the automation from the Approvers field:
{
"update": {
"Approvers": [{
"remove": {
"id":"{{initiator}}"
}
}]
}
}
You can learn more about in this KB, Advanced field editing using JSON
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.