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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Smart values field name trigger

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 

2 answers

1 accepted

0 votes
Answer accepted
John Funk Community Leader Dec 11, 2020

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. 

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?'

Workflow.PNGemail.PNG

John Funk Community Leader Dec 11, 2020

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. 

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

@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}}
Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

577 views 15 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you