StageTime documentation
StageTime shows how long Jira issues spend in each status, plus cycle time and lead time. It is made by Selana Technologies LLC. Support: hello@selana.io, first response within 1 business day.
Where to find it
- Report page: Apps menu, then StageTime. Also in each project's sidebar (the report starts with that project).
- Issue panel: open any issue and look for Time in status in the right-hand sidebar.
Run a report
- Enter a JQL query, or keep the default (issues updated in the last 30 days, or 90 days on a project page).
- Choose days or hours.
- Choose Calendar time (24/7) or Working hours (see below).
- Optionally choose Group by: Assignee, Issue type, Priority, Sprint or Parent.
- Click Run report.
You get:
- Stat tiles: issues analyzed, median cycle time, median lead time, average cycle time, and the 85th percentile ("85% of issues finish within").
- By status: average time per status as a chart, and a table with issues, average, median, 85th percentile and total time per status.
- By group: one row per assignee, issue type, priority, sprint or parent (whichever you chose in Group by) with issues, done, median cycle time, 85th percentile cycle time, median lead time and throughput (issues done per week over the last 12 weeks). Change the grouping at any time; the table updates without running the report again. An issue is counted in its active sprint, or its latest sprint if none is active. Issues with no value are listed as Unassigned, No sprint, No parent and so on. Sprint needs Jira Software.
- Trend: a chart of issues done per week and a chart of the median and 85th percentile cycle time of the issues done each week, for the last 12 or 26 weeks. Weeks start on Monday in the time zone set on the form (the working hours time zone, which defaults to yours). A week with no finished issue has no cycle time point. With Working hours, cycle times are working time.
- By issue: every issue with its cycle time, lead time and time in the six statuses that took the most time. Sort any column.
- Copy to spreadsheet: tab-separated text. Select all, copy, and paste into Excel or Google Sheets. One row per issue, one column per status. When a grouping is chosen, the group table follows the issues. For a formatted .xlsx, use the Export these issues to Excel with SheetOut link under the By issue table or on this tab. It opens SheetOut with the report's JQL filled in (SheetOut is a separate app; the link to its listing is next to it).
StageTime reads issues 100 at a time and shows progress (for example "Read 2,300 of about 5,100 issues"). Click Stop and show what was read to see a report for the issues read so far. Reports cover up to 20,000 issues. If your query matches more, StageTime tells you and summarizes the first 20,000; narrow the JQL by project or date. The summary always covers every issue read. The tables and the spreadsheet tab list at most 5,000 issues (the ones with the longest lead time or age); for a full file with every issue, export with SheetOut.
Working hours
Choose Working hours in the Time list to count only time inside your working week:
- Working days: default Monday to Friday.
- Hours: default
09:00-17:00. Split shifts are allowed, for example09:00-12:00, 13:00-17:00. - Time zone: default your own time zone, as a name like
America/New_York. - Holidays: dates as
YYYY-MM-DD, separated by commas. Holidays count as zero working time.
Time in status, cycle time, lead time and the chart then show working time, and the labels say "(working hours)". These settings apply to the current run only; StageTime does not save them. The issue panel always shows calendar time.
Dashboard gadget
Add Time in status (StageTime) to any Jira dashboard: Edit the dashboard, Add gadget, search for StageTime. In the gadget settings choose:
- JQL: the issues to measure (default: updated in the last 30 days).
- View: Average time per status (a bar chart) or Cycle and lead time (median and 85th percentile).
- Time: calendar time (24/7) or working hours, Monday to Friday 09:00-17:00 in your time zone.
The gadget reads up to 1,000 issues and says so when your query matches more. Open full report opens the StageTime report page with the same JQL and runs it, with no limit of 1,000.
How times are calculated
- Time in status adds up every visit to a status. The current status counts until now.
- Cycle time runs from the first time an issue entered an In Progress status to the last time it entered a Done status. Only done issues have a cycle time.
- Lead time runs from creation to that same Done moment.
- Status categories (To Do, In Progress, Done) come from your Jira workflow settings.
- Times are calendar time (24 hours a day, 7 days a week) unless you choose Working hours.
Permissions and privacy
StageTime reads Jira as the signed-in user, so people only see issues they already have access to. It stores no data and sends nothing outside Atlassian. See the privacy policy.
Troubleshooting
| You see | Do this |
|---|---|
| No issues match | Widen the JQL, for example remove the date filter. |
| Reached the 20,000 issue limit | Narrow the JQL by project, issue type or date. |
| Stopped early | You clicked Stop. Run the report again to read every issue. |
| Working hours: ... is not a valid time zone | Use a name like America/New_York or Europe/London. |
| JQL error | Check the query in Jira's issue search first, then paste it here. |
| Needs an active subscription | A Jira admin can start a trial or subscription in Manage apps. |
Pricing
Free for up to 10 users. See the Marketplace listing for current prices.