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

[Makarand Gomashe]

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:

• Field Value Changed Trigger

• Smart Values Supported by Trigger

Thanks,
Makarand Gomashe
Product Manager, JSM

[Felix Haverkamp]

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

[janez hribar]

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?

[Jason Prinsen]

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

[Cory Tsang]

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.

[Eric Bergeron]

RIGHT! Thanks Felix.

[Eric Bergeron]

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?

[David Brown]

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?

[Joseph Chung Yin]

@Makarand Gomashe -

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

Best, Joseph