Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I calculate the time issues spend on the backlog before being started?

AlexVasili March 8, 2022

Hi there, 
I am using cycle time to record the time issues spend from Ready to Done. This tells me the average time issues spend once they are active. I am looking for a way to record the time issues spend in the backlog before they are prioritised (moved to Ready), is there a straight forward way to do this? 

Thanks

5 answers

1 vote
Zoryana Bohutska _SaaSJet_
Atlassian Partner
March 8, 2022

Hi @AlexVasili 

To the solutions described above, you can consider SLA Time and Report. This app allows calculating SLA for issues from any type of project (Jira Software, Jira Core, JSM). For your case you can configure timer with such conditions: start - issue created, stop -  any status (To Do, In progress, etc). After you will be able to get the report with data about the amount of time issues were in the backlog. 

2022-03-08_15-01-52.png

Also you can try app Time in status for Jira Cloud. It automatically calculates time in each status, total issue age, and average time in each status. No matter when you will install this add-on, it will show also historical data. 

2022-03-08_15-13-56.png

 2022-03-08_15-13-18.png

All those apps are developed by my team, so let me know if you have any questions

AlexVasili March 11, 2022

Thanks for taking the time to put this together, I will see how this works for me. 

0 votes
Zane eazyBI Support
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 11, 2022

Hi @AlexVasili 

If you do not mind using 3rd party app, you might take a look at "eazyBI for Jira" (https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?hosting=cloud&tab=overview). 

With eazyBI, you may analyze Jira issues by different criteria, logged hours, time spent in each status, resolution time, story points, group issues by different field values, etc. 

You might take a look in the eazyBI Demo account to see a few ready-to-use report examples: 

How much time issues spent in the selected statuses: 
https://eazybi.com/accounts/1000/cubes/Issues/reports/61947-issue-days-in-selected-status

Currently unresolved issues by the age and priority. You may add Status as a page filter for this report to see only Backlog issues: 
https://eazybi.com/accounts/1000/cubes/Issues/reports/50398-unresolved-issues-by-age-interval-and-priority

eazyBI reports are flexible:

- Users can use report filters to select the reporting period, projects, issue priority, and other issues.
- Users can interact with reports to see which issues are behind each number.
- You can adjust those reports to match your use case. For example, add more dimensions to pages for filtering data or group statuses according to swimlanes.

Best,

Zane / Support@eazyBI.com

0 votes
Rahul_RVS
Atlassian Partner
March 8, 2022

Hi @AlexVasili 

If you are fine with a marketplace app, you can try out our add-on to get this data

The main features of the app are as below
  • 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 Transition 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.

 

TIS.PNG

AlexVasili March 11, 2022

Thanks for your suggestion, I will explore this further. 

0 votes
Mehmet A _Bloompeak_
Atlassian Partner
March 8, 2022

Hi @AlexVasili

You can use Status Time Reports app developed by our team. It provides reports on how much time passed in each status.

It has grouping feature so that by grouping statuses(In Progress → In Review → Done) you can get total time. You can also export the report as CSV and open it in Excel.

Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.

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

If you are looking for a free solution, you can try the limited version Status Time Free.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters 

Hope it helps.

0 votes
Emre Toptancı _OBSS_
Atlassian Partner
March 8, 2022

Hello @AlexVasili ,

Control Chart and Cumulative Flow Diagram may help you with that. They are available as part of standard Kanban Board reports. They both allow you to report on Backlog statuses. They don't show individual issues but can give you a good overall picture of your process.

 

If you need to see this for individual issues or you need more flexibility, 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  tisCloud_AssigneeDuration.png     

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

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.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

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

Suggest an answer

Log in or Sign up to answer