Time in Status for Jira — Documentation

Last updated: 29 July 2026.

Time in Status shows how long every issue in a Jira project has spent in each workflow status, plus lead time, cycle time and the project's slowest working status. Everything is computed from the issues' own change history — nothing to configure and no backfill.

Requirements

• Jira Cloud. The app runs entirely on Atlassian Forge; there is no server to host and no account to create.
• Works in both company-managed and team-managed projects.
• Installing requires a Jira site administrator, because the app asks for the read:jira-work scope at install time. After installation, any user who can open the project can use the page.

Installation

1. Install from the Atlassian Marketplace listing for Time in Status for Jira, or in Jira go to Settings → Apps → Find new apps, search for the app and choose Get app.
2. Review the requested permission (read:jira-work, read-only) and confirm.
3. The app appears under Settings → Apps → Manage apps, where it can also be uninstalled again.

Where to find it

The app adds a single project page. Open any Jira project and choose Time in Status from the project sidebar (under Apps, depending on your Jira layout). The page always reports on the project you opened it from — there is no separate configuration screen and no global admin page.

Using Time in Status

1. Open the page. It loads the project's issues and reads each issue's changelog, then computes the timings live. Nothing is precomputed or cached, so the numbers are current every time you open it.
2. Read the bottleneck banner. At the top, the app names the working status where issues spend the most time on average. Statuses in Jira's Done status category are excluded, so a finished issue sitting in Done forever cannot skew it.
3. Scan the table. One row per issue: current status, lead time (creation to done), cycle time (first move into an in-progress status until done), time in the current status, total tracked time, and one column per workflow status.
4. Filter by current status with the dropdown above the table to narrow the list to, for example, everything sitting in review.
5. Open a single issue from the table to see its per-status breakdown, sorted from slowest to fastest, with its lead and cycle time and whether it is completed.
6. Check the averages table below the issue table for the project-wide average time per status, slowest first, with the number of issues behind each figure.
7. Export CSV. The Export CSV button opens a dialog containing the full table as CSV text, including one column per status. Copy it and save it as the suggested filename to open it in a spreadsheet.

Statuses are matched on their Jira status id and grouped using Jira's own status categories (To Do / In Progress / Done), so renamed and localised status names are handled correctly and no per-project mapping is needed. The app has no scheduled job: it only does work while you have the page open.

Limitations

• 50 issues per project. The page reports on the 50 most recently created issues in the project, to stay inside the Forge function time budget. When that cap is hit, the page says so explicitly.
• Changelog depth. Up to 1,000 changelog entries are read per issue. An issue with more history than that is reported as truncated rather than silently miscounted.
• Elapsed (calendar) time only. Durations are wall-clock: nights, weekends and holidays count. There is no working-hours calendar or SLA configuration.
• History only goes as far back as Jira's changelog. If a status change was never recorded in the issue changelog, it cannot be reconstructed. Issues with no recorded status change are treated as having sat in their current status since creation.
• Single project at a time. There is no cross-project or portfolio roll-up view, and no JQL input — the scope is the project the page is opened in.
• Issues are read with the app's own permissions, not the viewing user's, so the report covers every issue in the project — including issues an individual viewer might not otherwise be able to open. Only issue keys, summaries, statuses and timings are shown.
• No file download. The CSV export is copy-and-paste from a dialog; the app does not write files or send them anywhere.
• Read-only, no persistence. The app stores no data of its own, so it has no saved reports, no history snapshots and no e-mail or subscription delivery.

Support

Questions, bug reports or feature requests: info@kyc-checks.nl. Please include your Jira site URL and the project key so we can reproduce the issue.