nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the smartvalue for "original estimate" or any time estimate in lookupissues in eJira ?

Arun Prince

I have tried below values and none of them fetch the data.

{{issue.timetracking.originalEstimate}}
{{issue.timeoriginalestimate}}
{{Original Estimate}}
{{timetracking.originalEstimate}}
{{issue.timetracking.originalEstimateissue.timetracking.originalEstimateSeconds}}

Accepted answers

Arun Prince

Hi @Trudy P Claspill

Thanks for your quick response.

We are currently on Jira Data Center and moving to cloud mid 2027.
Am trying to create a automated sprint end report and am able to fetch all values except Original Estimate. PFA screenshot.
Yes the issue has Original Estimate value.
If I replace Original Estimate with Story Point {{"Story Points".round}}, it fetches the value. But I am looking for Original Estimate filed value.
Below is the entire smart value

{{#lookupIssues}}<tr><td style="border:1px solid #e2e6ec;"><a href="https://xxx/browse/{{key}}" style="color:#0b66c2;text-decoration:none;font-weight:600;">{{key}}</a></td><td style="border:1px solid #e2e6ec;">{{summary}}</td><td style="border:1px solid #e2e6ec;">{{assignee}}</td><td align="center" style="border:1px solid #e2e6ec;">{{issue.fields.timetracking.originalEstimateSeconds}}</td><td style="border:1px solid #e2e6ec;">{{issuetype.name}}</td><td style="border:1px solid #e2e6ec;">{{status.name}}</td></tr>{{/lookupIssues}}

Screenshot 2026-10-15 at 9.15.45 PM.png

Shaik Riyaz

Hi @Arun Prince ,

Option 1:
The correct smart value is {{timetracking.originalEstimate}}.

Inside the {{#lookupIssues}} loop, drop the issue. prefix since the context is already scoped to each returned issue. Outside the loop, use {{lookupIssues.timetracking.originalEstimate}}.

Option 2:

Use {{timetracking.originalEstimate}}.

Inside a {{#lookupIssues}} loop, don't include the issue. prefix:

{{key}}: {{timetracking.originalEstimate}}
{{/}}
(Note: {{issue.timetracking.originalEstimate}} refers to the trigger issue, not the looked-up issues).

Thanks!!

CelesteCS

Hi, I'm Alexey 'Ce' from CelesteCS, the vendor of the app below.

Since time tracking isn't available inside {{lookupIssues}} on Data Center, an alternative for the sprint-end numbers is a Confluence page that reads them from Jira. With our Math for Confluence one formula gives the sprint total in hours:

SUM(JIRAISSUEFIELDVALUESBYFIELDID("sprint = 'Sprint 42' AND issuetype not in subTaskIssueTypes()", "aggregatetimeoriginalestimate", 0)) / 3600

Change the JQL per row (per status, team or sprint) to build a small summary table:

The Σ (aggregate) field includes the Sub-task estimates, and 0 is used for issues without an estimate. Your sprint-end rule can then simply send the page link. The formulas are the same on Data Center and Cloud, and the app supports the Data Center to Cloud migration, so the report moves with you in 2027.

Worked example: A sprint-end report with Original Estimate totals, without Automation. The app: CelesteCS Math for Confluence (free trial).

All comments

Trudy P Claspill

Hello @Arun Prince

Welcome to the Atlassian community.

Are you working with Jira Cloud or Jira Data Center?

Can you share with us your entire automation rule, and the details of the step where you are trying to use the smart value? Sometimes problems are about the context.

Have you confirmed that the issue you are trying to access has an Original Estimate value, and that issue is in focus in rule at the point you are trying to use the smart value?

This KB provides some examples of smart values for Original Estimate.

https://support.atlassian.com/automation/kb/automation-based-on-time-tracking/

This comment on another post also provides relevant information

https://community.atlassian.com/forums/discussion/comment/2832847#Comment_2832847

Arun Prince

Hi @Trudy P Claspill

Thanks for your quick response.

We are currently on Jira Data Center and moving to cloud mid 2027.
Am trying to create a automated sprint end report and am able to fetch all values except Original Estimate. PFA screenshot.
Yes the issue has Original Estimate value.
If I replace Original Estimate with Story Point {{"Story Points".round}}, it fetches the value. But I am looking for Original Estimate filed value.
Below is the entire smart value

Screenshot 2026-10-15 at 9.15.45 PM.png

Trudy P Claspill

Thank you for that additional information.

It is important to note that you are trying to get the smart value within the context of iterating over Lookup Issues results.

Getting time tracking values in that context is not supported. Refer to

https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

thanks to @John Funk for posting that information here

https://community.atlassian.com/forums/discussion/comment/2756013#Comment_2756013

Shaik Riyaz

Hi @Arun Prince ,

Option 1:
The correct smart value is {{timetracking.originalEstimate}}.

Inside the {{#lookupIssues}} loop, drop the issue. prefix since the context is already scoped to each returned issue. Outside the loop, use {{lookupIssues.timetracking.originalEstimate}}.

Option 2:

Use {{timetracking.originalEstimate}}.

Inside a {{#lookupIssues}} loop, don't include the issue. prefix:

{{key}}: {{timetracking.originalEstimate}}
{{/}}
(Note: {{issue.timetracking.originalEstimate}} refers to the trigger issue, not the looked-up issues).

Thanks!!

Tomislav Tobijas

@Arun Prince To add a small tip: you can also open the following URL directly in your browser (while logged into Jira; I use it in Cloud, though, but I believe the same/similar thing should work for DC):

https://<JIRA-URL>/rest/api/2/issue/<ISSUE-KEY>

This returns the JSON representation of a work item, so you can inspect how fields and their values are stored in the background. That's usually my go-to trick when checking field names and values. 😄

Of course, finding a field in the JSON doesn't necessarily mean it's accessible through automation smart values, especially within lookupIssues, but generally it is. 👀