Reports App Documentation

Overview

This app helps teams analyze how work moves through Jira statuses over time. It supports both issue-level and member-level reporting, filtering by project or sprint, and time calculations based on a configured work calendar.

The app is especially useful for understanding workflow bottlenecks, time spent in each stage, rework patterns, and team workload distribution.

Documentation pages

Dashboards — explains the table and chart view workflow, including collapsing the top controls to focus on the report.
Historical Duration Report — shows how long issues spent in each Jira status over time.
Last Duration Report — focuses on the most recent time spent in each status.
Entrance Date Report — shows when issues entered each status.
Entrance Count Report — counts how often an issue entered a given status.
Transitions Report — explains how issues moved between statuses.
Member Total Report — aggregates total time by member and status.
Member Last Report — shows the most recent member time by status.
Member Entrance Count Report — counts how often a member re-entered a status.
Member Transitions Report — tracks status movements by team member.
Member Duration Report — explains how much time each member spent on an issue or issue set.
Filtering Issues — explains how to scope the report using projects, sprints, saved filters, or JQL.
Calendar Setup — covers work hours, work days, timezone, and holidays.
Status Groups — explains how to regroup Jira statuses into broader process stages.

What each report is used for

The app supports several reporting patterns, each designed for a different question:

Historical duration: used to measure total time spent in each workflow stage across the selected period.
Last duration: used to review the most recent time spent in a status and highlight current bottlenecks.
Entrance date: used to see when work entered a status and understand timing across the process.
Entrance count: used to spot repeated re-entry and rework in a workflow stage.
Transitions: used to identify how work moves between states and where it gets stuck or loops.
Member total: used to measure team workload by status and contributor.
Member last: used to monitor the latest effort distribution by person.
Member entrance count: used to reveal repeated member-level re-entry and status churn.
Member transitions: used to understand how each team member is moving work across statuses.
Member duration: used to attribute contribution and time spent on issues to a person.

Key features

Flexible issue filtering with project, sprint, saved filter, or JQL.
Custom workday and holiday configuration.
Custom status grouping to represent workflow stages more clearly.
Table and chart views for review and export.
Members can shrink or expand the top controls to focus on the report and switch quickly between charts and tables.
The expanded state is stored so the app remembers whether the top controls are shown or collapsed.
Member and issue-level reporting to support both process and capacity analysis.