nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smart values field name trigger

Jack Garrod

Hi,

I have set up an automation to send an email when a field is changed. I have managed to put in the email via smart value what the field was changed from and to, but is there a way to smart value import the actual field name itself.

The automation works by looking at 6 fields on an issue (there are 12 fields on the issue in total) and if one of those 6 changes then the email is sent.

Thanks

Accepted answers

John Funk

Hi Jack,

I think you need to put a label for the field in the actual email. It will look a little wonky but will be descriptive. Or you could copy and past the email component and use a separate email component for each field.

All comments

John Funk

Hi Jack,

Jack Garrod

Thanks for the reply - i'm not quite sure I understand your reply. i currently have this set up such that when one of the values in the field listed change it shoots an email - I want one of the detail in the email to be 'what was the field that changed called?'

John Funk

Ah, that helps me to understand. I don't think you are going to be able to put the actual name of the field in the email like that. Just the values.

I was suggesting a different Rule for each field changed. For example, modify the rule to just fire when the Report Type changes. Then in the email body, put Report Type: in front of <b> {{field ....

Then copy that rule and sub out the field for the Description.

One problem will be that they will get multiple emails for the same issue if multiple fields change.

Bill Sheboy

Hi @Jack Garrod

Have you tried {{fieldChange.field}} as that seems to work for me to give the name.

And...after the "new view" goes into effect, it'll only ever be one field at a time per edit by user (right?) so no need to worry about only the first change being captured in fieldChange, which is what happens today.

Best regards,

Bill

Alexey Paveliev_pgpak4

@Bill Sheboy @Jack Garrod

I can confirm this worked for me as well

changed from [ {{fieldChange.fromString}} ] to [ {{fieldChange.toString}} ] by {{initiator.displayName}}
field name is {{fieldChange.field}}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud