Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,646,746
Community Members
 
Community Events
196
Community Groups

How do I set custom value changes as a trigger?

I made a dropdown custom field called "Status" and I want to post a comment every time the custom field changes so that it's more specific about what the status was changed from and by who. I have the automation on Butler set like this: 

Custom field Status automation Oct 17 2022 at 11 49 AM.pngwhich works as expected when the the status changes from a set value to another. However, when it goes from blank to a set value, it produces a comment that looks like this: 

Custom field Status automation comment from blank Oct 17 2022 at 11 50 AM.png

What steps do I need to take to make it so that when the dropdown custom field goes from being blank to having a value, the {customfieldvaluebefore} variable defaults to something like None or N/A? Is that possible? Does Butler support triggers based on when a custom field changes from something to another with dropdowns?

1 answer

You'll need to create 2 rules for this. 

I used "Text" Custom fields, but Dropdowns should work too. I also used quotes instead of asterisks. See below for the rules I used. Let me know if this is what you're after! 

image.png

Hi, sorry for the late response. I just tried this out and unfortunately, it produces the same result as shown in the screenshots of my initial post. I'm looking for a trigger that checks for when a custom field goes from being empty (not set) to filled (set), to post a comment that simply mentions what the value was changed to. It looks like the extra automation only checks for when that value is cleared, but I'm looking for when it goes from empty to set. 

I'll check again, but in my initial testing of this automation, my automation worked.

When you checked, did you have your first automation rule turned off before you tried the automations I provided? 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events