Sum remaining estimate in epic

Configuration

To use the Total remaining estimate in epic template, simply select it from the template grid. Filter by KPI to find it faster.

Parameters

This template does not require any additional parameter configuration.

Expert mode

Expression

General expression:

%{%{issue.issueType} = "Epic" ? sum(append(fieldValue({issue.remainingEstimate}, issuesUnderEpic()), [0])) / 60 : null}

If the resulting number from the expression contains too many decimal numbers, feel free to select one of the available display formats or to configure it manually.

Display as

Number

Formatting style

Default (unformatted)

Used parser functions

• sum()

• append()

• fieldValue()

• issuesUnderEpic()

Details

1. What does the expression do?

This expression calculates the total remaining estimate in hours for all work items under the current epic, excluding sub-tasks. If the current work item is not an epic, it returns “None”.

2. Step-by-step breakdown

Let’s break it down:

• %{issue.issueType} = "Epic"
  Checks if the current work item is an epic. If it is, the calculation proceeds; if not, it returns null (which displays as “None”).

• issuesUnderEpic()
  Retrieves all work items that are directly under the current epic excluding sub-tasks.

• fieldValue({issue.remainingEstimate}, issuesUnderEpic())
  For each work item under the epic, this gets the value of the "remaining estimate" field.

• append(..., [0])
  Adds a zero to the list of remaining estimates to prevent errors.

• sum(...)
  Adds up all the remaining estimates from the work items under the epic.

• / 60
  Converts the total from minutes to hours (since Jira stores remaining estimates in minutes).

• : null
  If the current work item is not an epic, the expression returns null (shows as “None”).

3. Examples

• If you are viewing an epic with three work items under it, and their remaining estimates are 120, 60, and 30 minutes, the calculation would be:
  (120 + 60 + 30 + 0) / 60 = 210 / 60 = 3.5 hours

• If you are viewing a work item that is not an epic, the result will be displayed as “None”.

4. Real-life use cases

• Epic Progress Tracking:
  A project manager wants to see how much work (in hours) is left to do in an epic. This expression provides a quick summary of the total remaining effort for all work items in that epic.

• Sprint Planning:
  During sprint planning, teams can use this field to estimate how much work remains in each epic, helping with resource allocation and forecasting.

• Reporting:
  This field can be used in dashboards or reports to monitor the progress of multiple epics and identify which ones have the most work left.