Is there a standard sprint report which includes "time-in-column"?

[J.R. Massey]

looking to monitor duration and flow of tickets.  Are there reports which show duration in process phase.  And/ or how many times a ticket was returned to an earlier phase? 

Example: dev ticket goes back and forth with QA team vs a ticket that only made the path once. (no rework.)

[Mariana_Pryshliak_Saasjet]

Hello @J.R. Massey 

You can try Time between Statuses add-on (server version) from the Atlassian Marketplace. 

Here's the use case that shows duration in each project phase.

This add-on is developed by my SaaSJet team, so let me knowif you have any questions. 

Hope it will be helpful.

[Emre Toptancı _OBSS_]

Hello @J.R. Massey

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for 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.

       

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.

The app also has Transition Count and Status Count reports which show the number of times each transition and each status was used. These are perfect reports to count reopens.

 

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 sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

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

[Mehmet A _Bloompeak_]

Hi @J.R. Massey

Welcome to the Atlassian Community!

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

• You can select issue fields and statuses that you want to see in your report. It has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. 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.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

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.

[Rahul_RVS]

Hi @J.R. Massey 

Welcome to the community !!

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

Agile Tools : Epic Tree, Links Tree, Time in Status & Worklogs

 The app allows to group your statuses and define your own lead/cycle time and pull the time the time the issues were in those statuses. And how many  times was a ticket in each status. Also you can create dashboard gadgets for these reports.

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

[Jimi Wikman]

I think you can query this using the API, but there are no reports as far as I know.

You probably could use automation to update a custom field somehow, but it seems like a lot of work :)

May I ask why you need this tracked? Is it for SLA purposes towards an external team? If so, then Jira is not the right tool, and you should look as JSM?

If it is to check if there is a problem with quality from the development team then I would take that as a team conversation. I have forced a DOD on occasion to stop sloppy work, but usually it is better to have the conversation.