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; } } }

Unable to Populate Original Estimate in Jira Automation Sprint Report

Neha

Hi Community,

I'm working on a Jira Automation sprint report and am trying to populate the total Original Estimate for all issues in a sprint.

I have a Lookup Issues action using: Sprint = {{sprintId}} which successfully returns all sprint issues. However, I'm unable to retrieve Original Estimate values, original Estimate is either return 0 or blank.

The issues themselves do have Original Estimates populated in Jira (e.g., 16h on individual issues).

Has anyone successfully retrieved and summed Original Estimate values from a Lookup Issues action in Jira Automation?

If so, what smart value or approach should be used?

Thanks in advance for any guidance.

Accepted answers

All comments

Trudy P Claspill

Hello @Neha

Welcome to the Atlassian community.

When asking for help with an Automation rule it will help us help you if you provide a screen image showing your entire Automation rule. Also show us the detail of the steps where you are trying to access the Original Estimate value.

Are you working with Jira Data Center or Jira Cloud?

If you are working with Jira Data Center, accessing the time tracking values through issues that are part of a Lookup Issues results set is not supported as per

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

Neha

Thanks for the reference. We are working with Jira Data Center.

I reviewed the documentation and understand that lookupIssues supports only a limited set of properties.

Is there documentation that explicitly lists the supported lookupIssues properties for Jira Data Center?

In my testing:

{{lookupIssues.first.summary}}
work correctly, but:

return blank/0 even though the issues have Original Estimates populated.

Is Original Estimate (Time Tracking) currently unsupported in lookupIssues for Jira Data Center, and if so, what is the recommended workaround?

Trudy P Claspill

Hello @Neha

I provided you a URL from Atlassian's own publicly visible Jira tracking system showing an unresolved backlog item asking for support for time tracking attributes via the {{lookupIssues}} smart value. Since it is unresolved that indicates there is no support for that.

JIRAAUTOSERVER-877

The issue also includes a link to the documentation for what is supported. If you access that documentation you will find it goes directly to the section concerning the attributes available with the Lookup Issues smart value

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

Arkadiusz Wroblewski

Try logging {{webhookResponse.body.issues.first.fields.timeoriginalestimate}} , then test the sum.

CelesteCS

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

As Trudy and Josh explained, {{lookupIssues}} on Data Center cannot read time-tracking fields. If the sprint report can live on a Confluence page (the sprint-end email then just links to it), our Reporting for Confluence reads the estimates straight from Jira through the application link and totals them:

Reporting Table View with a Reporting Jira Data Provider. Query: sprint = "Sprint 42" AND issuetype not in subTaskIssueTypes() Fields: summary,status,aggregatetimeoriginalestimate,aggregatetimespent,aggregatetimeestimate
A column for the estimate: IF(ISNUMBER(CurrentItem.fields.aggregatetimeoriginalestimate); CurrentItem.fields.aggregatetimeoriginalestimate / 3600; 0) with Footer aggregate: Sum (and the same for logged and remaining time).

The Σ (aggregate) fields include the estimates of Sub-tasks, so they are counted once, through their parent. The page reads Jira every time it is opened, so it is always current at sprint end.

The full configuration: A sprint-end report with Original Estimate totals, without Automation. The app: CelesteCS Reporting for Confluence (free trial, Data Center and Cloud).

Levente Szabo _Midori_

@Neha

since {{lookupIssues}} can’t read time tracking on Data Center, one way to keep the report inside Jira Automation is to have the rule generate the report file instead of adding up the total in a smart value.

With Better Excel Exporter and the free Better Excel Automation app, the rule needs two changes:

Keep your trigger and your sprint JQL, and tick “Process all issues produced by this trigger in bulk”, so the whole sprint goes into one file instead of one email per issue.
Replace the Lookup Issues step with the Send Excel action, which emails the spreadsheet to whoever needs the report. Original Estimate comes out as hours (Jira stores it in milliseconds and the app converts it), and the aggregated value that includes sub-task estimates is available too. The sprint total is then a plain SUM formula in the Excel template.

I think the bigger win is that the same template can carry time spent, remaining estimate and story points next to the estimate, or a pivot table by assignee, so the sprint report is one file rather than a set of smart values. When someone needs it outside the rule, the same export also runs from the Backlog for all issues in a sprint.

Here’s the step-by-step guide for the Send Excel rule. I’m one of the people at Midori building these apps, so feel free to drop our support team a line if you want help shaping the template.

Cloverkite

Hello @Neha

Building on Trudy's and Arkadiusz's replies: since {{lookupIssues}} can't read time tracking on Data Center, you can fetch the same issues through Jira's own REST API inside the rule and sum the field there.

Replace Lookup Issues with Send web request: method GET, tick "Wait for response", URL: {{baseUrl}}/rest/api/2/search?jql=sprint={{sprintId}}&fields=timeoriginalestimate&maxResults=1000 Header Authorization: Bearer <personal access token> of an account that can browse the project (a dedicated read-only account is safest, since the token sits in the rule).
Log {{webhookResponse.body.issues.fields.timeoriginalestimate}} first to check you get a list of numbers.
Then I believe {{webhookResponse.body.issues.fields.timeoriginalestimate.sum}} gives the total.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software