nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Metric - Frequency of Status?

Bud Herz_4dzuwt

Challenge -

Find way to identify how often a bug has been in a certain status.

Example -

Ticket failed by QA returns to Dev team in To-Do status three times because ticket isn't fixed correctly.

Question -

Is there a way to capture that as a metric in a dashboard? We know we are spending more time on certain tickets, but need a way to quantify it at a glance for the higher-ups who monitor dashboards.

Accepted answers

Bud Herz_4dzuwt

Actually I figured it out and didn't need an addon.

I created a custom field to increment a number. We called ours "QA Churn"

Using an automation in the project it increases by one each time a ticket transitions into that status.

I use this -
{{#increment}}{{issue.QA Churn}}{{/}}

A chart on my dashboard lists tickets to show the count from this field.

Easy peasy

All comments

Rahul_RVS

Hi @Bud Herz

If you are ok with a marketplace app to get this data (count in each status) you can try out our app.

Time in Status Reports

The add-on provides the time in each status for the entire lifecycle of the issue and you can filter by issue type as well. You can also combine your statuses to define your lead/cycle/resolution time and also extract the transitions history of the issues. The main features of the app are as below

Also there is a report for the dates when issue transitioned from one status to another.

Multiple Time in Status Reports. Excel Export available for all status reports.
- Time in Status
- Time with Assignee
- Time in Status with Assignee
- Time with Assignee per Status
- Status/Assignee Count
- Multiple Transition Reports
- Avg Time in status reports
- Status Change Dates Report
- Time in Status Per Time Grain
- Time with Assignee Per Time Grain
Status grouping
Save your reports
CSV Export
Multiple chart types
Dashboard Gadget

Disclaimer: I work for RVS, the vendor for this app, and I am one of the developers of the app

Mehmet A _Bloompeak_

Hi @Bud Herz

There is a good solution for your request - Status Time Reports app developed by our team.

By default, it provides reports on how much time passed in each status. But it also shows status entry counts (in your case how many times an issue has been in "To Do" status). You can also export the report as CSV and open it in Excel.

Here is the online demo link, you can see it in action and try without installing the app. Hope it helps.

Anthony Kozlov_SaaSJet_

Hi @Bud Herz

If you want to identify how often an issue has been in a certain status, I suggest trying the Time in Status for Jira Cloud add-on developed by my SaaSJet team.

Here are examples of two types of reports you can try:

Status count

unnamed (1).png

Transition count

Also, you try other features to track:

- time in status reports for Jira issues

- how long colleagues have been assigned to the issues

- average time spent in each status

- the date when the issue has entered each of statuses

All those data you can explore Pivot Table view, share on Jira Dashboard, and export to CSV and XLSX files

You can check the trial version or order a demo call. Let me know if you have any questions.

Emre Toptancı [OBSS]

Hello @Bud Herz ,

Our team at OBSS built Timepiece - Time in Status for Jirafor this exact need. It is available for Jira Server, Cloud, and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee.

tisCloud_StatusDuration_LeadTime_with Estimates.png

The app also has Status Count and Transition Count reports that show how many times each status and each transition was used. This is exactly what you ask.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

And the app has a REST API so you can get the reports from Jira UI or via REST.

Using Time in Status you can:

See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
Export your data as XLS, XLSX, or CSV.
Access data via REST API. (for integrations)
Visualize data with various chart types.
See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

Roberts Čāčus - eazyBI

Hi @Bud Herz ,

Others have already suggested good options. Another app you can consider is eazyBI - https://marketplace.atlassian.com/apps/1211051.

Delivering reports on Issue history and status transitions is just one of the aspects of its functionality. For example, the first iteration of a report with your requirements could look similar to the one below:

Screenshot 2022-01-21 at 17.45.35.png

You can filter the report results by other aspects, for example Priority, Affect version, time period of the transitions, etc.

You can start a free trial and experience other options eazyBI can offer or explore the eazyBI Demo account - https://eazybi.com/accounts/1000/dashboards/14871-chart-types.

I hope you will find what you are after.

Roberts // support@eazybi.com

Bud Herz_4dzuwt

Actually I figured it out and didn't need an addon.

I created a custom field to increment a number. We called ours "QA Churn"

Using an automation in the project it increases by one each time a ticket transitions into that status.

I use this -
{{#increment}}{{issue.QA Churn}}{{/}}

A chart on my dashboard lists tickets to show the count from this field.

Easy peasy

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud