How can I get the value of cycle time per assignee

[Shrushti Shah]

I want to measure some KPIs at the team and individual levels since I want to streamline the development process. In order to create a report on it, I must compute the following metrics for each team and individual:

1. Cycle Time
2. Time for Code Review
3. QA Cycle
4. Story rollover to another sprint ratio (Planed Stories)

I am unable to figure out how to measure every single thing. If there are any plugins available for it. Can anyone help for the same?

[Mehmet A _Bloompeak_]

Hi @Shrushti Shah

Welcome to the Atlassian Community!

There is no built-in solution in Jira for the reports you need. If you prefer using a marketplace app, 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.

Here is the online demo link, you can see it in action and try without installing the app. For your cases:
1. Cycle Time: You can have a look at Cycle Time for Each Issue and Cycle Time by Assignee reports.
2. Time for Code Review: If you are using a status like "Code Review" for the issues in code review, then you can have a look at Time in Status for Each Issue report. "Code Review" column will give you the time passed on code review.
3. QA Cycle: If you are using more than one statuses for the issues in QA cycle, then you can group these statuses and get QA cycle.

For further details, you can have a look at  Status Time Reports How to Videos.

App Features:

• This app 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.

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

If you have any questions, feel free to schedule a demo with us.

Hope it helps.

[Mehmet A _Bloompeak_]

Hi @Shrushti Shah ,

For the last case Story rollover to another sprint ratio (Planed Stories), you can try Reports - Charts and Graphs for Jira app developed by our team.

We will be happy to explain how to achieve it in your Jira. Feel free to schedule a demo with us.

[Hannes Obweger - JXL for Jira]

Hi @Shrushti Shah

welcome to the community!

As you can see from the previous answers, this is an area where many Jira users rely on apps from the Atlassian Marketplace to fulfil their status time reporting needs. 

If a Marketplace app is an option for you, I think you might like the app that my team and I are working on, JXL for Jira. 

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSM-specific fields - much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren’t natively available, including time in [status], time between [status] and [status], time with [assignee], time with [assignee] in [status], and many, many more.

This is how it looks in action:

As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

You may already know that you can trial any app for free for 1 month, so if an app is an option for you, perhaps try a few and see which one works best for you and your team!

Any questions just let me know,

Best,

Hannes

[Iryna Komarnitska_SaaSJet_]

Hi @Shrushti Shah ,

If I may suggest, you need to measure the Time Between Statuses metric more. Because you need to measure transitions between statuses precisely.

My team has created such an app.

You create a group status and have the opportunity to see the calculation in the report. You can set up notifications for yourself if the time limits are exceeded.

Here is a 30-day trial; if you have any questions, contact our support or book a demo call. I hope this will be useful to you!

[Amay Purohit_RVS]

Hi @Shrushti Shah 

Welcome to the community !!

You can use Jira Rest API's to build your own custom solution and track time spent by your assignees for overall issue cycle. Or for a readymade solution, a mktplace app can help here. If you are open to try out one, do take a look at

Time in Status Reports 

One of the many reports which the app provides is Time with Assignee in hours/days to determine , how much time the issue spent with each assignee in the complete lifecycle of the issue. You can also group your statuses to determine the cycle times.

The app has 20+ reports to meet a variety of time in status use cases.

More Details here 

Disclaimer : I work for the vendor who built this app

[Gizem Gökçe _OBSS_]

Hello @Shrushti Shah ,

Welcome to the community!

In order to measure Cycle Time, Time for Code Review and QA Cycle I would recommend using a third-party app, as there is no built-in solution in JIRA for this.

My recommendation is Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center. 

Timepiece mainly allows you to see how much time each issue spent on each status and on each assignee/group/team. 

Timepiece offers two report types for your case:

The first one is Assignee Duration per Status report  which shows how much time each assignee spent on each Status. 

        

The second one is Group Duration per Status report which shows how much time each Group/Team spent on each Status.

  

For both of the reports you can combine the time for multiple statuses to obtain metrics according to your specifications, such as Cycle Time, Time for Code Review and QA Cycle, etc. Also, you can calculate averages and sums of those durations grouped by the issue fields you select. All these options can provide both calculated data tables and charts. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

[Polina-DevAcrobats-]

Hello Shrushti, welcome to the community!

I’m part of the team that developed the Performance Objectives: Charts & Reports for Jira Dashboards. Our app extracts essential Jira metrics such as Time in Status, Time in Assignee, Cycles in Status, Cycles in Assignee, Time Between and Cycles in Sprint, which are required for the reports you mentioned. Moreover, you have the flexibility to filter story points based on rolling state, commitment state, completion, and scope change for sprint-by-sprint metrics. You can utilize formulas to calculate ratios and set targets directly on your Jira dashboard. On our website, you can find a variety of KPI report examples for Jira that can inspire you.

Kind Regards,

Polina