Tempo Account smart value not applying in summary

Aaron Geister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 22, 2024

I have tried to use all three tempo account smart values to add the tempo account to a summary of an issue and non of them work or apply.

  • {{issue.TempoAccountField}} - Returns the name of the account

  • {{issue.TempoAccountField.name}} - Returns the name of the account

  • {{issue.TempoAccountField.value}} - Returns the name of the account

    Is there only specific places that this smart value will work?

    In my automation in summary I have add all three of this and tested but none of them will apply the account. Does the account have to be set on the issue before it can apply or can it pull from the parent issue?

    I have tried this when account is available and still not working.

2 answers

2 accepted

1 vote
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 22, 2024

Hi @Aaron Geister 

Try this smart value:

{{issue.Account.value}}

Or this, for the parent potentially...

{{issue.parent.Account.value}}

Note: I haven't tried these, found it mentioned in this answer from a Tempo team member.

Ste

Aaron Geister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 1, 2024

Thanks @Stephen Wright _Elabor8_  Bingo

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2024

Hi @Aaron Geister 

First thing, I am not using Tempo, and my suggestions are based on what I know about automation rules.  With that out of the way...

You are referring to this information, correct?  https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.TempoAccountField--

Some marketplace apps add custom fields for their data, while others dynamically generate the data using code.  In automation rules, this can have the impact of some smart values appearing as null in some usage.

The way to check that is:

  • Try writing the values to the audit log versus updating the summary field.  If that works...
  • Try saving the values using the Create Variable action first, then use the variable to update the Summary

Kind regards,
Bill

Aaron Geister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 1, 2024

Thanks @Bill Sheboy  I should always use audit log checking to validate the automation and always for get to add that into my automation. Thank you again.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events