Add a label using Automation, without changing/removing existing labels

[Alex Bernardin]

Using the Automation add-on, I want to have a rule/action such that on a specific transition, a label gets added to the labels field.

When I set this up using the 'Edit field' action, I found that the new label would be applied, and existing labels would be removed. 

Wondering if there is a different action I can use to add a value to a field without replacing the existing field value?

[Alex Bernardin · Accepted solution]

aaaaaand, as so often happens, I've answered my own question.

When you use the Edit Field action, there's a text field for entering the new value.  To the right of that field there's an elipsis overflow menu icon.  Clicking that icon gives you options for adding or removing explicit values from the field, instead of just replacing the field. 

[Angelo C]

Thanks for this post. I got caught in this and didn't see the hidden menu.

For the sake of clarity, the top field is for values you want to add to the issue.  If you want to keep the other values intact, you leave the bottom field blank.

[Tom Stratton]

What Angelo said!

[Doug Reading]

Same here. I completely missed this, thanks for sharing!

[Sylvain Leduc]

Hello @Alex Bernardin 

Interesting, I thought the field "organization" as a label too, was working like "labels" but there is no such extension (3 dot button) for it. Unfortunately.

[Alex DePaul]

@Alex Bernardin Any thoughts as to why Component/s doesn't give me the option to Add/Remove values?  

[Julia Anderson]

This 'add/remove' setting is still replacing existing labels for me and not adding. Any help would be appreciated!

[Harald.Conradi]

@Julia Anderson 

I learned the hard way today that all previous labels were removed when Automation added my "Sprint/Planned" label.

Based on the above tips (thanks, all!), I've made edits.

I'm using ... > Add/remove values

1. Top Row is "Values to add" - the label I want to add
2. Bottom row is left blank (based on above tips), so that should leave the other, pre-existing Labels values intact.

I'll find out in 2 weeks if this worked as intended. :-)

[Julia Anderson]

Thanks for the response @Harald.Conradi. I am also using that solution to no avail.  

[Alex DePaul]

Hi! The fix for me was to select "copy from issue" and then add the new label. 

[Erik Starke]

Hi, this is what I did @Alex DePaul with 5 automations that all shall set different labels but not overwrite each other. The automation result is a "success" whenever the condition is met, but it still overwrites them. Oddly enough, SOMETIMES there are 2 labels though.
That made me double check but no, all rules are configured with the "Copy from issue" attribute.
Anybody with an idea? 

[Stephen Aroza]

Facing the same issue. 2 automation rules to add labels are overwriting each other even when the rule is added with Add/remove values.

From what I see, the issue is because both automations are running simultaneously and label just changes from None -> label

Is there a way we can introduce a delay on some automations?

[Erik Starke]

Hey Stephen, I found a solution to my problem. 
After adding 1 label via automation, you can use another automation action called "Re-fetch issue data". 
If you use that, the automation will update the labels and keeps them if you wanna add more than one.

[Stephen Aroza]

Thanks, @Erik Starke! This definitely helps alleviate many cases. However, still found cases where one of the labels is being overwritten. Feel there might not be a solution to this?

[BG Pantaleon]

Same issue here. I tried re-fetch but still getting overwritten by another Label.