The Time in Status report shows how long issues spend in each Jira status, highlights the bottleneck in your workflow and reports the lead time and cycle time of every issue. It is calculated from the status change history of each issue, so it works with any workflow without additional configuration.

Available as:

• Report page: menu Reports Time in Status.
• Dashboard gadget: "Time in Status" gadget, which can be added to any Jira Assistant dashboard multiple times with different settings. It replaces the older "Status Wise Time Spent" gadget and existing gadgets are upgraded automatically.
• Jira Cloud dashboard widget: "Time in Status" widget from the Jira Assistant Cloud app (shows the Bottlenecks view).

Click the icon to open the settings. Under Data source, choose how the issues are selected:

• Custom JQL: all issues matching the JQL, e.g. project = ABC AND issuetype in (Story, Bug).
• User groups: issues assigned to the members of the chosen user groups, optionally narrowed with an additional JQL filter. Choose the users with the icon in the header, or the groups saved under Settings User Groups are used.

Under Period, choose whether the report is based on a Date range (default) or on Sprints.

• Date range: pick a preset (Last 30 days, Last 90 days, Last 6 months, Last 12 months, This year, All time) or a custom range from the header. Issues that were open at any time within the range are included.
• Sprints: see the section below.

Agile teams can analyse the flow of one or more sprints instead of a date range.

• In settings, set Report based on to Sprints and choose one or more boards in Agile boards. The boards configured under Settings General Default Values are pre-filled.
• The report header now shows a sprint button ( ). Click it to open the sprint picker, which has a card for each board.
• Tick the boards to include and choose Last sprint, Last closed sprint, Last 2 to 5 sprints, or Choose sprints to pick specific sprints. Sprints are listed with their state and dates, and can be searched when a board has many sprints.
• Click Apply to load the report, or Cancel to discard the changes. The button shows what is selected, e.g. "Team board · Last 2 sprints".
• Issues that are part of any of the selected sprints are included, along with your JQL or user group scope. Relative choices such as "Last sprint" move to the new sprint automatically once it starts.

Note: durations are not limited to the sprint dates. The full status history of each included issue is measured, so an issue carried over from an earlier sprint shows its complete time in each status.

• Summary cards: number of issues (in progress and resolved), median lead time, median cycle time and the bottleneck status.
• Bottlenecks view: one row per status with issues currently in it, issues that passed through it, and the average, median, maximum and total time. The In Progress status with the highest average time is highlighted as the bottleneck. Click a status to see its issues sorted by time spent.
• Group by: split the statistics by project, issue type, assignee, user group or any Jira field, e.g. labels or components.
• Issues view: one row per issue with selectable columns such as lead time, cycle time, time in current status, time per status and a colour coded status timeline (proportional or calendar scale).

• Time spent in each status is calculated from the status changes in the history of every issue, starting from its created date. Repeated visits are added together.
• Lead time is measured from the created date until the issue is resolved. Cycle time is measured from the first move into an "In Progress" category status until the issue is resolved.
• Statuses are classified by their Jira status category (To Do, In Progress, Done), so the report works across different workflows.
• Turn on Count only working hours to exclude nights, weekends and other non-working time, based on the working days and hours in General settings.
• Status history is cached on your device and fetched again only for issues updated since the last run, so repeat runs are fast. On Jira Data Center, you are asked to confirm before fetching the history of a large number of issues.
• The report can be exported to CSV, Excel and PDF from the menu in the report header.