How can we get multiple fields changed - Automation mail

[Sreenivasaraju P]

Hi,

I am trying to send a mail using automation. In this the mail, I want to send the update the fields. We are updating multiple fields and want to send their previous and updated values.

I have tried using {{fieldChange}} smart value. It is supporting only one field. Is there any option or alternative for this to send the field changes of multiple fields.

As per Altassian documentation, When there are multiple fields that have changed, {{fieldChange}} only contains the first changed value. 

Automation smart values - issues | Cloud automation Cloud | Atlassian Support

Is there any other alternative or solution for this . 

Thanks in Advance,

[Trudy Claspill]

Hello @Sreenivasaraju P 

Have you already got a rule constructed? If so, please share with us screen images showing your entire rule. Also provide detail images for anyplace where you are using smart values or JQL.

Explain to us what you expect to have happen when the rule executes, and what you actually observe happening.

Also, it will be helpful if you provide a screen image showing all the details of the Audit Log entry created when the rule executed.

And lastly, what is the scope for your rule? Is it single project, multiple project, or global?

[Bill Sheboy]

Hi @Sreenivasaraju P 

Yes, and...to the suggestions from @Trudy Claspill 

Although documentation for the {{changelog}} smart value indicates it supports multiple fields, in my experience, that is only relevant for a small number of scenarios.  Thus, another key question is: how are you changing the work item's multiple fields?

It appears the automation engine is selective regarding which events lead to which triggers starting a rule.  For example...

• Transitioning a work item Status could lead to field changes (i.e., Rank), and thus multiple events (and so possibly multiple rules starting)
• A single work item update of multiple fields (other than Status) using the REST API (or JSON with a rule edit) might lead to only one event
• Attachment, comment, worklog, etc. updates are all additional scenarios, and so potentially leading to different events
• And...there are known defects where the changelog supplied to rules can be inaccurate for list fields, such as Sprint, Fix Versions, etc., reducing the value for your scenarios
• And...there are changes which do not create changelog entries; for example, some addons / apps have their own changelog, such as for checklists

When one wants to see mostly everything that changed in a small window of time, a brute-force way to do that is to grab the changelog records with the REST API and to parse them for the time range.

Kind regards,
Bill