/
๐Ÿ“˜ How to Use Flow Time Report

๐Ÿ“˜ How to Use Flow Time Report

Get full visibility into issue status timelines โ€” effortlessly.

๐Ÿงญ Overview

Flow Time Report is a Jira Cloud app that visualizes how long an issue spends in each status. It enables product managers, scrum masters, and engineering leads to detect bottlenecks, optimize workflows, and assign control badges like ๐ŸŸข ON TRACK, ๐ŸŸก AT RISK, or ๐Ÿ”ด OVERDUE.

Frame 105.png

๐Ÿš€ Getting Started

  1. Open any issue in Jira.

  2. Click the Flow Time Report panel.

    Frame 104.png

ย 

  1. Wait for the app to load the changelog โ€” usually takes a second.

  2. View status transitions, time spent, and assign badges.

  3. Export the data via the Export button if needed.

๐Ÿ“‹ Table Columns Explained

Frame 107.png

Column

Description

Column

Description

Status

The name of the Jira status the issue was in (e.g., To Do, In Progress, Done). If an issue enters the same status more than once, each entry is listed separately in chronological order.

Time

The total time the issue spent in this specific status. Calculated based on the issue's changelog. Format: days, hours, minutes.

Status Badge

A visual indicator of how healthy the time spent in this status is:
๐ŸŸข ON TRACK โ€” within the acceptable threshold
๐ŸŸก AT RISK โ€” moderately exceeds the threshold
๐Ÿ”ด OVERDUE โ€” significantly exceeds the threshold
โšช NOT SET โ€” no badge applied (either not selected or manually unset)

Changed By

The user who transitioned the issue into this status. Pulled from the Jira changelog.

Changed At

The exact date and time when the issue entered the corresponding status.

๐Ÿ” Flow Status Row (the arrows at the top)

Frame 106.png

This row shows the exact flow of status transitions for the selected Jira issue, based on its real change history โ€” including repeated transitions.

TO DO โžœ IN PROGRESS โžœ IN REVIEW โžœ DONE โžœ IN PROGRESS

This means the issue:

  • Started in To Do

  • Moved to In Progress

  • Then to In Review

  • Was marked Done

  • And then re-opened or continued in In Progress

๐Ÿง  This overview helps you understand how the issue progressed, spot regressions, and identify back-and-forth movement across statuses.

๐Ÿงฎ Total Time

Frame 108.png

At the bottom, you'll see:

  • Total Time: the cumulative time spent across all statuses for this issue

  • Useful for evaluating full issue lifecycle time or average time in system

๐Ÿ“ค Export Time-in-Status Data from Any Issue

Frame 111.png

Export full status history and timing in CSV, JSON, Markdown, or Plain Text โ€” ready for reporting, analysis, or audits.

โ„น๏ธ More Info

Frame 109.png

Click the Info button below the report to access two options:
โœ” Close Info โ€“ Hide this information block.
โœ” Read More โ€“ Open full external documentation with details on how time is calculated, privacy policy, admin setup, and more.

๐Ÿงช How It Works

The app automatically loads:

  • Status history from the Jira changelog API (/rest/api/3/issue/... with expand=changelog)

  • Creation date of the issue

  • Duration per status (start to end of next)

  • Displays it in a structured table

  • Stores user-defined badge metadata in issue properties

๐Ÿ›ก Permissions & Data

Flow Time Report only reads:

  • Issue status history

  • Issue creation date

  • User display names

  • It stores badge selections in issue property badge-metadata

๐Ÿงฉ Tips for Teams

  • Add Flow Time Report to your Definition of Done

  • Use OVERDUE to flag SLA breaches

  • Export weekly CSV reports to share progress in standups

๐Ÿ’ก Best Practice

Assign badges right after sprint planning or during grooming to align expectations across the board.