Measuring Engineering Performance using Jira Cycle Time

[Gunawan Kosasih]

Hi folks, 

I gotta question about the cycle time feature on Jira. As we know cycle time is to measure team performance on delivering project or epic, similarly,the Cycle Time feature within Jira pretty much measures what is the status of an epic or bugs.

On Jira however, there's only stating collective engineer process(from PR to deploy), but there is no information for each individual PR to Deploy status on the Cycle Time feature. 

I wonder if there is any method using Jira to track the speed and performance of an engineer when they received or are assigned a ticket?

[Srikanth Upputuri]

Kanban helps you to out arrive Cycle Time & Lead Time.

We heavily used Kanban to retrieve Cycle Time/Lead Time/Throughput Rate.

Create the Statuses as per the Development life cycle.

For Eg: 

"In Progress", "Under Review","Under verification", "pending Staging".

Make sure Exclude "Done".

As part of the control chart select the above said statuses, then you are retrieving cycle time.

Do let me know if you need any information.

[Yuliia_Borivets__SaaSJet_]

Hi @Gunawan Kosasih 

You can check this article if you're looking for individual/assignee cycle time:

3 tools to analyze Cycle and Lead Time in the Jira

[Emre Toptancı _OBSS_]

Hello @Gunawan Kosasih ,

This will be the same answer to your other question but still worth mentioning here.

Jira's Cycle Time report shows this metric using Jira issues, commits, and deploys. I believe, tracking this using only Jira issues makes much more sense. Your issue workflow probably already has statuses that represent all stages in the lifecycle of a task. Reporting on how much time each issue spent on each status will give much more flexible results.

If you are OK with using a marketplace app for that, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center. 

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

       

Time in Status 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 perfect to get 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.

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

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Rahul_RVS_Support]

Hi @Gunawan Kosasih 

For an alternate solution, to get this data 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

[Oskars Laganovskis]

Hi @Gunawan Kosasih ,

I see that @Yuliia_Borivets__SaaSJet_  already offered several solutions for reporting and tracking performance with Jira Cycle time feature.

I might suggest yet another reporting app - the eazyBI app for Jira that allows creating simple reports and completely customized reports as well.
It allows one to see the totals and averages and also drill through assignees or projects down to each issue.

You may check the Demo account showing the dashboards created with eazyBI. The Age, Lead, and Cycle Time dashboard seem to cover your use case:
https://eazybi.com/accounts/1000/dashboards/7513-age-lead-and-cycle-time

The app is available for a 30-day free trial so you can make sure it fits your needs before making any commitments.

Kindly,
Oskars, eazyBI support