The Report Type parameter allows the user to select the type of the report. There are many different report types:
Duration Reports
Status Duration
Status Duration in the older and the most commonly used of the report types. Status Duration Report lists each issue in rows with statuses as columns and the time that issue spent in that status as column values.
This report helps you identify the bottleneck statuses in the workflow.
Status selection in this report allows you to exclude statuses (and their columns) from the report. It also allows you to consolidate status durations into Consolidated Columns.
Multi Visit Behavior and the Visit Count option under View Format are specific to this report type.
Related use case articles:
Duration Between Statuses
Duration Between Statuses Report allows you to define multiple metrics where each metric shows the duration between two statuses in the workflow. The report lists each issue in rows with metrics as columns and the duration for that metric as column values.
This reports helps you measure the performance of your process over multiple statuses.
While the Status Duration Report shows each status individually or consolidates specified statuses into Consolidated Columns, Duration Between Statuses Report shows the total duration between two statuses and does not require identifying the individual statuses between the start and end statuses.
See DBS Metrics page for details about Metric definitions.
Status Duration per Time-Period
Status Duration per Time-Period Report is a two level report that lists each issue in a row with status names and time-period names as columns and the time that issue on that status in that time-period as column values.
The Time-Period can be configured as a Year, Quarter, Month, Week or Day.
This report is similar to Status Duration report but instead of showing the status time as a single value, it shows that duration divided into time-periods. It is particularly powerful when used with aggregation options like Sum or Average. For example, when used with Sum, these reports can show you the total cost of various process stages over time. Similarly, when used with Average, these reports can show the change in performance of each process stage over time.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Time-Period Duration per Status
Time-Period per Status Duration Report is a two level report that lists each issue in a row with time-period names and status names as columns and the time that issue on that status in that time-period as column values.
The Time-Period can be configured as a Year, Quarter, Month, Week or Day.
This report is similar to Status Duration report but instead of showing the status time as a single value, it shows that duration divided into time-periods. It is particularly powerful when used with aggregation options like Sum or Average. For example, when used with Sum, these reports can show you the total cost of various process stages over time. Similarly, when used with Average, these reports can show the change in performance of each process stage over time.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Assignee Duration
Assignee Duration Report lists each issue in rows with user names as columns and the time that issue spent assigned to that user as column values.
This report helps you identify the bottleneck users in the workflow.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Related use case articles:
Assignee Duration per Status
Assignee Duration per Status Report is a two level report that lists each issue in rows with status names and user names as columns and the time that issue spent assigned to that user in each status as column values.
This report helps you identify the bottleneck users in the workflow.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Status Duration per Assignee
Status Duration per Assignee Report is a two level report that lists each issue in rows with user names and status names as columns and the time that issue spent on each status of each assignee as column values.
This report helps you identify the bottleneck users in the workflow.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Please note that seleting User as filter type and selecting Assignee Time as report type is completely unrelated. The former is just for filtering issues and the latter is about the type of calculation made
Group Duration
Group Duration Report lists each issue in rows with the user group names you select as columns and the time that issue spent assigned to a member of that user group as column values.
This report helps you identify the bottleneck user groups in the workflow. For example you can build and select groups like "Level 1 Support" and "Level 2 Support" to see the time issues spent assigned to members of those groups.
If any of the users are a member of more than one group, Time in Status shows a warning. Durations assigned to a user outside selected groups or durations when the issue was unassigned are shown as an extra columns, if any.
Status selection in this report allows you to exclude durations for unselected statuses from the report.
Related use case articles:
Group Duration per Status
Group Duration per Status Report is a two level report that lists each issue in rows with status names and user group names as columns and the total time that issue spent assigned to a member of that user group in each status as column values.
This report helps you identify the bottleneck usr groups in the workflow.
Status selection in this report allows you to exclude durations for unselected statuses from the report or define consolidated columns to view status times together.
Status Duration per Group
Status Duration per Group Report is a two level report that lists each issue in rows with user group names and status names as columns and the time that issue spent on each status of each userr group as column values.
This report helps you identify the bottleneck user groups in the workflow.
Status selection in this report allows you to exclude durations for unselected statuses from the report or define consolidated columns to view status times together.
Any Field Duration ADVANCED
Any Field Duration Report is the most advanced report type for durations. It allows you to see how long each issue field held each value. It helps you identify many different wait times in issue workflow, without having to define a status for them.
The report asks the user to pick at least 1 issue field and lists each issue in rows, possible values of the selected field as columns and the time each issue spent with that values as column values.
For example you can define a SelectList field named Vendor, configure your workflow to have your users select a vendor while transitioning to Waiting for Vendor status and clear the field when transitioning out of this status. If you prepare an Any Field Report and select the Vendor field for History Field, you will be able to see how much time your issues spent waiting for each vendor.
History Field panel allows selection of up to 5 fields so you can get reports broken down by values from multiple fields.
For example if your issues move from sprint to sprint, you can select Sprint and Status issue fields as History Fields and the report output will show you how much time each issue spent in each status under each Sprint.
Single/multi select, single/multi user picker, text and long text fields are supported. Epic Link, Affected/Fix Version, Sprint, Project, IssueType, Status, Assignee and many other fields are also supported.
Date, datetime, number and a few other field types are not supported since they do not make sense for this report type.
This report type also supports Status selection. If you make status selection, whatever fields you select as History Fields, the column values will include only the durations when your issues are in one of the selected statuses. The durations for unselected statuses will be excluded from the report. In other words, the counters will pause when the issue is in an unselected status.
Related use case articles:
- I am working with multiple vendors. How can I see how much time I spent waiting for each?
- I move issues from sprint to sprint. How can I see how much time my issues spent on each status under each sprint?
- My work is blocked by many third parties. How can I see how much time I lost waiting for each?
Count Reports
Transition Count
Transition Count Report lists each issue in rows with transitions as columns and the number of times that transition happened as column values.
This report shows you how many times a transition from one status to another happened so helps you identify most used workflow routes. Especially useful for complex workflows.
Status Count
Status Count Report lists each issue in rows with statuses as columns and the number of times that status was visited as column values.
This report helps you identify re-visits of statuses of particular importance. Especially useful for identifying reopens, blockages or information requests when these statuses are embedded as optional routes in workflows.
Any Field Count ADVANCED
Any Field Count Report is the most advanced report type for counts. It allows you to see how many times each issue field held each value.
The report asks the user to pick at least 1 issue field and lists each issue in rows, possible values of the selected field as columns and the number of times each issue had that values as column values.
History Fields panel allows selection of up to 5 fields so you can get reports broken down by values from multiple fields.
Single/multi select, single/multi user picker, text and long text fields are supported. Epic Link, Affected/Fix Version, Sprint, Project, IssueType, Status, Assignee and many other fields are also supported.
Date, datetime, number and a few other field types are not supported since they do not make sense for this report type.
Date Reports
Date Reports show status transition dates as report values.
There are four Date report types. All four types seem to show similar values but based on what you want to measure, each report type will stand out be more useful compared to others, especially if your issues tend to go back and forth between statuses.
First Transition To Status Date
First Transition To Status Date Report shows status names as columns and the FIRST date each issue transitioned TO that status as column values.
This reports helps you get the dates issues first arrived at each status you can compare them with your own targets like lead times, responses times, etc.
Last Transition To Status Date
Last Transition To Status Date Report shows status names as columns and the LATEST date each issue transitioned TO that status as column values.
This reports helps you get the latest dates when issues arrived to a given status so you can compare them with your own targets like resolution times, etc. Especially useful if issues go back and forth between statuses.
If an issue visited a status only once, First Transition To Status and Last Transition To Status reports will show the same date/time for that status.
First Transition From Status Date
First Transition From Status Date Report shows status names as columns and the FIRST date each issue transitioned FROM that status as column values.
This reports helps you get the dates issues first left each status you can compare them with your own targets like resolution times, etc.
Last Transition From Status Date
Last Transition From Status Date Report shows status names as columns and the LATEST date each issue transitioned FROM that status as column values.
This reports helps you get the latest dates when issues were in a given status so you can compare them with your own targets like resolution times, close times etc. Especially useful if issues go back and forth between statuses.
If an issue visited a status only once, First Transition From Status and Last Transition From Status reports will show the same date/time for that status.