Are smart values are different in new software projects

[Chris Sandford]

I am creating a new software board and trying to automate some emails. I am using the same smart values as im currently using on a projects board ({{issue.fields.summary}}) and nothing gets pulled through. 

The fields are called the same thing on both. I have also tried the list of other smart values and none of them are pulling through. (https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/) 

For the new software boards are the values different? Also, how can i see them? Im not an admin and have tried pulling via the API but these values arent showing in the response. 

[John Funk · Accepted solution]

Hi Chris - Welcome to the Atlassian Community!

You don't need the fields part in the middle. Just {{issue.summary}}

[Chris Sandford]

Hi John,

Thanks for the reply, it still didnt work though. Below you can see the values in Jira and on the right the email i get from it. 

[Bill Sheboy]

Hi @Chris Sandford 

Would you please post an image of your entire rule?  That will provide some context that might reveal what is happening.  Thanks!

Best regards,

Bill

[John Funk]

Can you share the audit log of the rule that you ran? It appears that no issue match whatever condition you might have in the rule. 

[Chris Sandford]

@Bill Sheboy Below is the email. Bottom part was to test values that were on the Jira site.

Hi {{issue.assignee}},

Workaround {{issue.summary}} is assigned to you on {{issue.created}}. Could you please keep us up to date with the progress of getting this resolved.
{{issue.description}}.

Business Solutions Team

Available properties
Issue fields

{{issue.description}} - Returns the content in the issue's Description field.
{{issue.key}} - Returns the issue's key, which is a unique identifier comprised of the project key and the issue's number. For example, PROJ-123
{{issue.status}} - Returns the issue's status
{{issue.status.name}} - Returns the issue's status
{{issue.summary}} - Returns the issue's summary
{{issue.versions}} - Returns the issue's Affects versions
{{issue.issueType}} - Returns the issue's type, for example Story, Bug, or Task.
{{issue.resolution}} - Returns the issue's resolution.
{{issue.updated}} - Returns the date the issue was updated. Can be combined with other date and time smart values. Learn more about date and time smart values.

{{issue.Story Points}} - Returns the issue's story point estimate (classic Jira Software Cloud only).

{{issue.Story Points estimate}} - Returns the issue's story point estimate (next-gen Jira Software Cloud only).
Issue dates

These can be combined with other date and time smart values. Learn more about date and time smart values.

{{issue.created}} - Returns the issue's creation date
{{issue.duedate}} - Returns the issue's due date.

Issue users

These can be combined with other user smart values. Learn more about user smart values.

{{issue.assignee.displayName}} - Returns the issue's assignee.
{{issue.reporter.displayName}} - Returns the issue's reporter.

[Chris Sandford]

@John Funk 

[John Funk]

There are no associated items that it ran against - which was what I suspected. Can you share the query you used under the When: Scheduled 7 days details? 

[Bill Sheboy]

If there is no JQL associated with that scheduled trigger, that would explain the problem...although it creates another symptom:

I thought the rule raises an error if there are no issues when you try to access issue smart values.  Curious...

Update: I just tried a scheduled rule without JQL, accessed an issue field, and it threw no errors.  Seems like something has changed in that behavior for the rule engine.

[Chris Sandford]

@John Funk this should have 1 and when i validate it says 1. 

[Bill Sheboy]

Please try to uncheck the checkbox: "Only include issues that have changed..."

[Chris Sandford]

@Bill Sheboy Thank you! I think thats the only setting i didnt try. Its now working. 

[Bill Sheboy]

Chris, would you please mark this one as solved/answered?  That will help others in the community find solutions faster.  Thanks!

[Chris Sandford]

@Bill Sheboy will do now. Thanks again.