How to Build Hierarchy Reports in Jira: Tasks, Epics and Initiatives

[#1]

Maintaining a flexible Jira hierarchy is key to aligning high-level business goals with daily engineering tasks. However, tracking exact status times across these structural tiers is a common roadblock for many delivery teams. Standard Jira metrics often fail to capture the true active duration of parent issues, leading to manual spreadsheet exports and skewed cycle times. Integrating precise time-in-status reporting directly into the Jira Agile hierarchy resolves these visibility gaps and helps teams spot bottlenecks early. 

Demystifying the Agile Hierarchy and Its Reporting Deficits

Jira builds structure by distributing work items (issues) from macro-level organizational strategies down to granular, daily deliverables. While this structure keeps teams aligned, native reporting limitations often obscure the actual time spent in each workflow state.

The table below maps the standard levels of the Agile hierarchy and the specific tracking challenges administrators face at each tier:

Hierarchy Level	Practical Business Purpose	Focus of Engineering	Native Reporting Deficit
Initiatives	Multi-quarter business goals that compile Epics from multiple teams	Macro-level progress tracking	Standard Jira cannot track or roll up status times above the Epic level out of the box
Epics	Large bodies of work representing unifying product features or milestones	Multi-week or multi-month execution	Epic status is static; it does not reflect the active duration of child issues
Stories	Sprint-sized goals written from the perspective of the end user	Problem-solving and functional delivery	Finding state bottlenecks (like Code Review) requires manual historical data analysis
Tasks & Subtasks	Technical actions, administrative work, and daily engineer assignments	Daily deliverables and individual tasks	High issue volume makes manual time aggregation impossible for teams

Organizations using Jira Premium or Enterprise with Advanced Roadmaps can customize their structures by adding custom levels above the Epic, such as Initiatives, Programs, or Themes. While these tiers are crucial for tracking long-term business goals, standard configurations fail to aggregate the active status times of underlying issues.

To bridge this visibility gap, Timepiece allows you to display these parent levels (such as Initiatives, Programs, Projects, or Themes) as individual columns directly within your detailed list reports, or use them to group and aggregate metrics.

Once configured, your detailed report will display the active parent-child associations along with the exact Cycle Time:

For example, a user story relies on the standard template: "As a [user], I want [goal] so that [reason]". Its lifecycle follows the three C's: Card (the written requirement), Conversation (backlog refinement), and Confirmation (acceptance criteria verification). While this structure supports delivery, the status of a parent Epic remains "In Progress" as long as any child story is open. Simply viewing the overall time an Epic spends in a state does not represent the real engineering hours invested. True visibility requires rolling up the active durations of all child stories, tasks, and subtasks.

Configuring True Epic-Level Progress Rollups

Tracking status times across custom parent containers, such as Epics or Initiatives, requires a dynamic aggregation method that pulls data directly from active workflows. Using Timepiece - Time in Status for Jira, administrators can automate this aggregation, eliminating the manual overhead associated with historical data extraction. This approach ensures that metrics represent the real-time status of the underlying engineering effort.

The table below outlines the exact configuration path to set up parent-level status duration rollups in the reporting interface:

Step	Action Required in Timepiece	Practical Outcome
Report Selection	Choose the target project and select the Status Duration report	Establishes the core tracking metrics for active workflow states
Aggregation Choice	Click the Report Options button and switch from the List option to the Sum option	Directs the system to calculate cumulative time across issues
Hierarchy Grouping	Select Hierarchy Level 1 (Epic) or custom tiers in the Report Options	Dynamically groups child issue durations under their parent containers
Metric Customization	Add specific statuses or create a Consolidated Column	Measures broader operational metrics like Cycle Time or Lead Time

When you configure these rollups, the report sums the durations of direct child records at the standard issue level, including Stories, Tasks, and their respective sub-tasks. Because Timepiece pulls these fields dynamically from your Advanced Roadmaps hierarchy, parent-level metrics update automatically without manual spreadsheet calculations. This setup provides a true view of delivery progress across specific workflow phases.

Optimizing Sprint Predictability at the Story and Task Level

While parent-level rollups assist with long-term planning, tracking status times at the Story and Task level helps teams resolve daily workflow bottlenecks and manage developer workloads. This granular monitoring shifts the focus from macro progress to sprint-level efficiency.

Identifying Workflow Bottlenecks

The Status Duration report measures exactly how long individual issues stay in each workflow state. For example, if user stories are consistently delayed in the "Code Review" status, this report highlights the exact step where work is stalling, allowing Scrum Masters to address the blocker during retrospectives.

Balancing Team Workloads

The Assignee Duration report tracks active working time per team member, including human developers or integrated AI agents. This visibility helps team leads identify resource constraints, prevent developer burnout, and ensure that tasks are distributed fairly across the engineering team.

Tracking Sprint Delivery Trends

Instead of analyzing raw, flat lists of individual tasks, teams can use the Report Options toolbar to switch from a "List" report to an "Average" or "Sum" report. By grouping the active data by "Sprint" and "Story Points," Timepiece automatically calculates the Average Cycle Time for specific story point values. This analysis shows whether higher-point stories are causing disproportionate delays, helping the team improve future sprint planning and estimation accuracy.

Aligning Jira Architecture with Pragmatic Status Reporting

A clean Jira Agile hierarchy provides a strong operational foundation, but structure alone cannot resolve workflow friction or balance team capacity. Combining clear parent-child relationships with accurate time-in-status reporting gives engineering leaders the visibility needed to keep sprint cycles on schedule.

Because Timepiece respects custom business calendars, tracking metrics exclude weekends, holidays, and non-working hours. This dynamic calculation, combined with native hierarchy fields pulled directly from Advanced Roadmaps, ensures that cycle times and epic rollups remain highly accurate without manual administrative work. This accurate data helps teams spot blocked tasks early and maintain predictable delivery timelines.

To start measuring exact cycle times and automating epic progress rollups, you can explore Timepiece - Time in Status for Jira on the Atlassian Marketplace.