Atlassian · Jira Cloud
StatusTime
Time in status, cycle time and workflow audit for Jira issues.
- Works with Jira Cloud
- Marketplace Atlassian Marketplace
Coming soon
Coming to the Atlassian Marketplace
StatusTime is an Atlassian Forge app. It is deployed and prepared for the Atlassian Marketplace, but it has not been submitted, approved or listed, and it cannot be installed by the public yet. This page exists so the address is stable when that changes.
Coming soon toAtlassian Marketplace
What it does
StatusTime is an Atlassian Forge app for Jira Cloud. It works with company-managed and team-managed software, service and business projects. For a project, a date range and an optional issue-type filter, it measures how long each issue spent in every status and the lead time (created to resolved) and cycle time (first In Progress status to resolved), rolls the time up by status category (To Do, In Progress and Done), and flags workflow problems: reopens, backward moves (backflows) and how long unresolved issues have sat in their current status. It can measure elapsed time as a 24/7 calendar or against a business-hours working calendar (working weekdays and hours in a time zone you choose). It reads from Jira, never writes to Jira, and the application stores nothing. Per-issue and per-status metrics export as CSV.
Capabilities
Time in status
For a set of issues, see how long each issue spent in every status, with the total, average, median and maximum across the set.
Lead time and cycle time
Lead time runs from created to resolved. Cycle time runs from the first move into a status in the In Progress category to resolved. A roll-up adds the time up by status category: To Do, In Progress and Done.
A workflow audit
Counts reopens (a move out of a Done-category status) and backflows (a move backward through To Do, In Progress and Done), and shows how long each unresolved issue has sat in its current status. Issues with reopens or backflows are highlighted.
Calendar or business hours
Measure elapsed time as a 24/7 calendar, or against a working calendar: pick the time zone, the working weekdays and the start and end of the working day. Business hours exclude nights and non-working days. Public holidays are not excluded.
Assignee hold time and oldest in status
See the total time each person was the assignee, and the unresolved issues that have waited longest in their current status.
CSV export
Download a per-issue CSV and a per-status CSV. Durations are written as decimal hours, your browser builds the files locally, and each file names the clock used.
In each project and under Apps
StatusTime adds a page to the sidebar of each project, and a global page under Apps where you choose a project you can browse.
Read-only, as the signed-in person
The app requests one read-only scope, read:jira-work. Every Jira read runs as the signed-in person, so a report shows only what that person may see. The app never reads Jira with its own identity and never writes to Jira.
The application stores nothing
No Forge storage, database, cache, scheduled jobs or queues. No external network calls, analytics, telemetry or externally hosted code or fonts. Your browser builds any CSV locally and saves it to your device when you download it. Atesen Software operates no server for it and cannot see your data.
Questions
Where does StatusTime run?
StatusTime is an Atlassian Forge application and runs on Atlassian (Runs on Atlassian). Atlassian hosts its code and processes its requests. Atesen Software operates no server or database for the application and has no access to customer data.
What does StatusTime connect to?
Only your Jira site. The application makes no external network calls and has no egress. It has no analytics, no telemetry and no externally hosted code or fonts. Every Jira read runs as the signed-in person, and the app never reads Jira with its own identity.
How do I get help with StatusTime?
Support for StatusTime is provided by email in English and Turkish.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- It has not been submitted to, approved by or listed on the Atlassian Marketplace and has no installation count, customer list or review history.
- It holds no security certification and has not undergone a third-party audit.
- A report covers at most 1,000 issues and a date range of at most 24 months.
- Business hours exclude nights and non-working days, but not public holidays.
- Lead time and cycle time exist only for resolved issues. Cycle time is blank for an issue that never entered a status in the In Progress category.
- It reads only what the signed-in person may see, so a report reflects that person’s access to Jira.
Marketplace
Atlassian Marketplace: Prepared for the Atlassian Marketplace — not yet submitted, approved, listed or installable.
Coming soon toAtlassian Marketplace