Trigger an automation rule on a change to either of two fields?

[Staffan Bergh]

If I enter two or more Fields in the automation trigger FieldChanged, are the two values AND-ed (ie the trigger only fires if both/all are changed) or OR-ed (ie it fires if any of the fields changed)?

And what value goes into the ''{{fieldChange}}" smartvalue, if two fields change?

Isn't clear from the docs ...

Or maybe I am barking up the wrong tree?

I have a few custom fields (like From and CC addresses from outside our domain) that change based on reception of an email by the Email This Issue app. I want to run an automation rule only once for those several changes. How do I acheive that?

[Gor Greyan]

Hi @Staffan Bergh

Welcome to the Atlassian Community!

When you add multiple fields to the “Field value changed” trigger, the logic is OR — the rule will fire if any one of the selected fields changes. It won’t wait for all of them to change at once.

If you need to access every field that changed, use the {{changelog}} smart value instead — that gives you details for each modified field.

Use like this.

For the Change From.

{{#changelog.From}}
From changed from "{{fromString}}" to "{{toString}}"
{{/changelog.From}}

For the Change CC:

{{#changelog.CC}}
CC changed from "{{fromString}}" to "{{toString}}"
{{/changelog.CC}}

[Bill Sheboy]

Hi @Staffan Bergh -- Welcome to the Atlassian Community!

When using the Field Value Changed trigger with multiple fields selected...

• The rule will trigger when any of the fields changed (i.e., it is an OR check)
• The rule will trigger for each field changed, and thus multiple rule executions when the fields are changed individually and / or over a period of time
• The changelog smart value will contain whatever changed for that specific rule triggering, one or many fields
• Exceptions to the above are:
  • There are known defects with the changelog provided to rules for some list fields (e.g., Sprint, Fix Versions, etc.) and so it cannot be relied upon for accuracy; thus, if you are checking a list field, ensure you test thoroughly
  • When the fields all change at one time (e.g., a single edit using workflow post function, REST API call, etc.) the rule will trigger one time, including all the changes
  • Some field changes have their own events, and thus will not trigger a Field Value Changed rule.  These include, but are not limited to: assignee; worklog; status; comments; and for team-managed projects, add / remove from a board.

Kind regards,
Bill

[Staffan Bergh]

OK, I think this answers my question -- adding the two fields to one `FieldChanged` may work or not: it depends on how (the app) Email This Issue works. I have a question out to the app developers.

[Valerie Knapp]

Hi @Staffan Bergh , welcome to the Atlassian Community and thanks for your post.

For help with automations, please can you provide some more information about the context?

First of all, is this a company-managed or team-managed project?

What is the trigger for the automation?

What are the conditions?

What are the actions?

Please can you share an anonymised version of the rule?

Please can you share the audit log and indicate to us what is going wrong / not working?

I also usually signpost people to the automation library for help getting started. See this rule - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/9919294 

Thanks and looking forward to helping!

[Staffan Bergh]

The trigger is `FieldChanged`, and the conditions I want to test for are changes in two custom fields in a company-managed project.

My problem isn't that the trigger fails -- my problem is that I want to combine two rules with different conditions, that both trigger fine, but does essentially the same thing.

Your example link is for a `FieldChanged` with *one* watched field. What happens if I set it to look at *two* fields, and both change as a result of a mail handler execution in (the app) Email This Issue? Will the rule trigger one time or two times?

The ultimate purpose is to save us automation rule cycles ... so we don't have to go to a Premium subscription ...