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?
Hello @Gunawan Kosasih
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.
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:
https://marketplace.atlassian.com/apps/1211756/
EmreT
Hello @Gunawan Kosasih
To solve your issue, as an alternative, you can try the add-on from the Atlassian Marketplace - Time in Status for Jira Cloud. It generates 7 types of time reports to get more detailed info about team's productivity.
It calculates Cycle time. You just need to Add new status group and get the necessary data.
Also, you can track how long it takes your colleague to solve the issue with the Time in Status report. And export it to XLSX or CSV files for further analysis using such tools as Excel or Google Spreadsheets.
Hope it helps.
You can have a look at the article below that includes details on how to get a report of "cycle time by assignee". Hope it helps.
Productivity Measurement with Two Critical Parameters: Cycle Time and Lead Time