Automations on Multi-choice and Labels

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

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes

Answer accepted

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.

Comment

Awesome, Thank you, Mikael. This works.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Mikael Sandberg likes this

Was this helpful?

Thanks!

Jira Service Management

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

PREMIUM

PERMISSIONS LEVEL

Product Admin

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Automations on Multi-choice and Labels

1 answer

1 accepted

Comments for this post are closed

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

PERMISSIONS LEVEL

TAGS

Atlassian Community Events