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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


“Field Value Changed” trigger enhanced to support “Change type” in A4J

Makarand Gomashe
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 15, 2022

Hi Everyone,

I would like to inform you that we have updated the "Field Value Changed" trigger in A4J (automation) to listen and understand different types of changes: Value added, value deleted, any changes to the field. One of these types can be selected as filter when adding this trigger to an automation rule. Now automation rules can differentiate different change types. For example, rules can now be triggered when an Organization or a Participant is added to an issue.

Read more:

Makarand Gomashe
Product Manager, JSM


Screenshot 2022-02-16 at 12.37.37 PM.png


Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 16, 2022

@Makarand Gomashe -

Excellent news.  Do you know if this new functionality is also available for Data Center installation?

Best, Joseph

When I use "Value deleted" the automation triggers if I delete a value. But it also triggers if I change the value. I assume that's because, behind the scenes, it is deleting and then adding the value when I make a change.

Is it possible to have this trigger only when a value is truly deleted and not simply changed?

I'm seeing the same problem. Stakeholders requested I add a comment when reopening, but we're seeing a lot of false positives when the field value changes.

I'm seeing the same thing as of 8/22/2022

When I have the change type (Value added) it will update on the initial add of the value but it will ALSO update when the value is updated/changed. This is undesirable and I'm guessing a bug.

Just confirming that it is still an issue

I have an automation(1) rule that is triggered by any changes made to a custom field "B" (single choice list) to modify field Due Date (which works), but when a seperate automation(2) that changes custom field "B" runs, the Automation1 does not trigger (no Audit log). 

Should automations pickup modifications done by another automation? Are changes recognized on single choice lists?

you can activate "this rule can be triggered by other automation rules" in the detail of the rule

Like Joseph Chung Yin likes this

RIGHT! Thanks Felix.

Problem: my field changed rule fires perfectly fine, modifying an other issue field value - however the change is not reflected on UI. A workaround is to close issue detail and reopen the issue again.  

Is there any idea how to make sure UI is refreshed with changed value?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events