Summary
Development and product teams can aggregate Jira time tracking fields for all work items belonging to an epic. Grouping by Epic helps teams compare estimated effort, consumed effort, and remaining work across major product initiatives.
Business value: Product owners can identify the initiatives (or the epics) consuming the most capacity, detect estimate overruns, and see where the largest amount of unfinished work remains.
Configuration
Explanation of this use case
Features or ideas are linked to their Epics to establish the “epic-children” relation. The following fields are added to each work item:
-
Original Estimate: A system field that tracks the planned estimate for a feature or idea.
-
Time spent: A system field that shows the time logged for a feature or idea.
-
Remaining estimate: A system field that shows how much time remains for a feature or idea. By default, it equals Original Estimate minus Time spent.
Please configure the Grouped Filter Results gadget as shown in the screenshot below to realize this use case.