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
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
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?
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.
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
I'll find out in 2 weeks if this worked as intended. :-)
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?
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?