Founding offer: 40% off the first payment on selected apps with code FOUNDING40, until 30 November 2026.40% off selected apps’ first payment: FOUNDING40 until 30 Nov. See founding prices

Atesen Software Find your appAll apps
Menu

StatusTime documentation

Documentation for StatusTime. It describes the application and its limits as they exist today. StatusTime is prepared for the Atlassian Marketplace but has not been submitted, approved or listed; it is not yet available to the public.

Requirements

  • Jira Cloud and at least one project you can browse. StatusTime works with company-managed and team-managed software, service and business projects.
  • StatusTime appears as a page in each project’s sidebar and as a global page under Apps, where you choose the project.
  • StatusTime is a paid app, to be sold through the Atlassian Marketplace once it is listed. Running a report requires an active licence in production; a missing or inactive licence blocks it. The licence is checked on every backend call.
  • A browser that allows downloads from your Jira site, to save the CSV files.

Run a report

  • Open StatusTime from the project sidebar, or from Apps for the global page, and choose the project if the page asks for one.
  • Choose the date field to filter on: created, resolved or updated.
  • Set the from and to dates. The range can be at most 24 months.
  • Optionally choose which issue types to include.
  • Choose the clock: a 24/7 calendar, or business hours. For business hours, choose the time zone, the working weekdays and the start and end of the working day.
  • Run the report.
  • Download the per-issue CSV or the per-status CSV. Your browser builds each file locally and saves it to your device.

How the metrics are defined

  • Time in status: how long an issue stayed in each status, taken from the issue’s status history (the Jira changelog). The report shows the total, average, median and maximum per status across the set of issues.
  • Lead time: from created to resolved.
  • Cycle time: from the first move into a status in the In Progress category to resolved.
  • Category roll-up: the time added up by status category — To Do, In Progress and Done.
  • Reopen: a move out of a status in the Done category.
  • Backflow: a move backward through the To Do, In Progress and Done status categories.
  • Aging: how long an unresolved issue has sat in its current status. The oldest-in-status view lists the unresolved issues that have waited longest.
  • Assignee hold time: the total time each person was the assignee.
  • Issues with a reopen or a backflow are highlighted in the report.

Calendar and business hours

The calendar clock counts every elapsed hour, day and night. The business-hours clock counts only the working weekdays and the working hours you set, in the time zone you choose, so nights and non-working days are excluded. Public holidays are not excluded.

Both CSV files name the clock that was used.

What is in the CSV files

  • A per-issue CSV, with the metrics for each issue.
  • A per-status CSV, with the metrics for each status across the set of issues.
  • Durations are written as decimal hours.
  • Your browser builds the files locally, and the application does not keep a copy.

Permissions

StatusTime requests exactly one read-only scope. Every Jira read runs as the signed-in person (Forge asUser), so a report shows only what that person may see. The app never calls asApp and never writes to Jira.

  • read:jira-work to search issues and read fields, status history (the changelog), project statuses and the browse permission.

Limits

  • At most 1,000 issues per report.
  • A date range of at most 24 months.
  • Business hours do not exclude public holidays.
  • Lead time and cycle time are calculated only for resolved issues.
  • Cycle time needs the issue to have entered a status in the In Progress category and to be resolved. Otherwise it is blank.
  • A report shows only what the signed-in person may see in Jira.
  • StatusTime does not write to Jira.

Troubleshooting

  • A report will not run and points to the licence: running a report requires an active licence in production, and a missing or inactive licence blocks it. Ask your Jira site administrator to check the app’s licence, then try again.
  • The project is missing or cannot be read: every read runs as you, so you can report only on a project you can browse. Ask a project administrator for access, or choose another project.
  • The report is empty: check the date field (created, resolved or updated), the from and to dates and the issue types. Widen the range or include more issue types.
  • Cycle time is blank for an issue: cycle time needs the issue to have entered a status in the In Progress category and to be resolved. Lead time and cycle time exist only for resolved issues.
  • The figures are larger than expected: the calendar clock counts every hour, including nights and weekends. Switch to business hours and check the time zone, the working weekdays and the working hours. Public holidays are not excluded either way.
  • You expect more than 1,000 issues: a report covers at most 1,000. Narrow the date range or the issue types and run it again.
  • A download is blocked: your browser builds the files locally, so allow downloads for your Jira site in the browser’s site settings and download again.

Data handling summary

The application stores nothing. Jira data passes through a Forge function in memory for the length of each request and then to your browser, which builds any CSV locally. There are no external network calls, and nothing is written to logs. The application privacy page has the full statement.

Atesen Software security policy