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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to run automation on custom field and smart values using LookupIssues

I need a rule that will run on schedule, check JQL and send a list of tickets to a user.

I have issues with smart values when "send email"

Here's the email content:

Key+Summary: <a href="{{url}}">{{Key}} - {{summary}}</a>
All comments: {{comment}}
Returns last comment: {{issue.comments.last.body}}
Custom field value: {{issue.10033}}


When an email gets triggered I get blank values I miss {{issue.comments.last.body}} and {{issue.10033}}

2 answers

1 accepted

1 vote
Answer accepted

Hi @tasha tokunova 

When your rule is inside of the {{lookupIssues}} you no longer use the {{issues...}} prefix to the smart values.  Their context is the lookup, and {{issues...}} refers to other contexts, such as either the trigger issue or issues within a branch.

Please try this: inside of the lookup iterator  {{comments.last.body}}

Kind regards,

Oh wow! Thanks, Bill, it works! 

{{comments.last.body}} fixed


Do you know how to fix smart value to return custom filed body?

Custom field value: {{10033}}

This doesn't return the value ^

I think I was able to find the answer, this is the way to go:

Custom field value {{fields.customfield_10033}}

Thanks @Bill Sheboy again! 

Like # people like this

I am glad to learn that helped!

By the way, when you are trying to find the correct smart values to use for a field, this how-to article can help.  Basically you find an example issue and call the REST API from a browser tab to list all possible smart values.

Like tasha tokunova likes this

@tasha tokunova thank you for the custom field syntax. It wasnt described anywhere

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events