Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA Cloud - in automation, how to add a new label, not edit the label

Benjamin Zhou
Contributor
August 11, 2026

JIRA Cloud - in automation, how to add a new label, not edit the label.

I don't want to overwrite current label, if I want to add a new label, how to do?

Screenshot 2026-08-12 134056.png

2 answers

1 accepted

2 votes
Answer accepted
Chris Hampshire
Contributor
August 11, 2026

Hello @Benjamin Zhou 

In order to add a new label in your automation, you'll need to set the automation action as "Edit Work Item" and select  labels from the fields.

From here, it defaults to "Set" which means to add a label without overwriting what is there

If you want to simultaneously Add or remove labels, you can click the 3 dots to the right of the field and select ADDREMOVE and this will give you that option

Benjamin Zhou
Contributor
August 11, 2026

@Chris Hampshire  Ok, I see.  According to your reply, I found the add option.  Thank you very much for your help!

Like # people like this
0 votes
Andrey - Guenov Labs
Atlassian Partner
August 12, 2026

Adding one nuance to Chris's answer above, since it's specific to the visual editor and there's a common follow-up gotcha:

If you ever need to switch that same Edit Work Item action to the Advanced / smart-values (JSON) editor — for example because the label needs to be computed dynamically rather than picked from the field list — the behavior changes. In Advanced mode, "labels": ["new-label"] genuinely does overwrite the array; there's no implicit "Set = merge" behavior there like there is in the visual field editor. To append instead, you need to reconstruct the full list explicitly:

{{issue.labels.add("new-label")}}

or, if you're building the array from scratch:

{{issue.labels}}, new-label

(then split/rejoin as needed depending on how you're assembling the JSON body).

One more thing worth knowing if multiple automation rules touch labels on the same issue: even the visual editor's "Set" is a read-then-write of the whole list under the hood, so two rules firing close together on the same issue can still race and clobber each other's label. If that's a realistic scenario for your rules, the explicit ADD/REMOVE mode Chris mentioned is safer than Set for exactly that reason — it's additive rather than replace-the-whole-list.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events