What is the smart value for "original estimate" in lookupissues in Jira data center?

[Simon M]

What is the smartvalue for "original estimate" or any time estimate in lookupissues in Jira data center?

For {{issue}} the following works

issue.timetracking.originalEstimate
issue.timetracking.originalEstimateSeconds

For {{lookupIssues}} I have tried the following syntax but none of them work and it is pretty poorly documented.

lookupIssues.Original Estimate
lookupIssues.originalestimate
lookupIssues.originalestimation
lookupIssues.timetracking.originalEstimate
lookupIssues.timetracking.original estimate
lookupIssues.fields.timetracking.originalEstimate
lookupIssues.fields.timetracking.original Estimate
lookupIssues.Ursprüngliche Schätzung
lookupIssues.timetracking.Ursprüngliche Schätzung
lookupIssues.estimate
lookupIssues.estimation
lookupIssues.originalestimate
lookupIssues.originalestimation
lookupIssues.timetracking
lookupIssues.timetracking.timespent
lookupIssues.timetracking.remainingestimate

Adding ".sum" at the end always return 0. Also I have checked the JQL. I do get data back in {{lookupIssues}} for example with {{lookupIssues.key}} or {{lookupIssues.summary}}

Version v9.12.2 Data Center

[John Funk · Accepted solution]

Hi Simon,

I don't think that field is currently available for Data Center. You should vote for and follow this request: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

Also, here is the current documentation showing the currently available fields:

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-lookupissues-properties

Look under the Available properties section under Lookup Issues. 

[Bill Sheboy]

Hi @Simon Ma 

As John described, the time tracking fields are not supported for the Data Center version of the Lookup Issues action yet.

Two possible workarounds for this depend upon what you want to do with the value(s):

• Want to access / sum the fields for use in an email or message, and your rule does not need a branch to do so
  • Use the bulk-handling feature of branches or the scheduled trigger.  With this feature, the plural {{issues}} smart value is available and the list function such as sum will work.  Please look here to learn more: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
• Want to use the fields to edit another issue (e.g., update a a total in an issue)
  • Using the Send Web Request action, call the Jira REST API for issue search with JQL.  The response will contain all the fields, and those can then be used with the list functions.  If you want to try that, here is a how-to article for that technique: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Kind regards,
Bill