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

Run a report

  1. Enter a JQL query, or keep the default (issues updated in the last 30 days, or 90 days on a project page).
  2. Choose days or hours.
  3. Choose Calendar time (24/7) or Working hours (see below).
  4. Optionally choose Group by: Assignee, Issue type, Priority, Sprint or Parent.
  5. Click Run report.

You get:

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:

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:

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

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 seeDo this
No issues matchWiden the JQL, for example remove the date filter.
Reached the 20,000 issue limitNarrow the JQL by project, issue type or date.
Stopped earlyYou clicked Stop. Run the report again to read every issue.
Working hours: ... is not a valid time zoneUse a name like America/New_York or Europe/London.
JQL errorCheck the query in Jira's issue search first, then paste it here.
Needs an active subscriptionA 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.