If I need to view cycle-time for a particular issue using "Control Chart", how to view it?

[Vinay Sharma]

In control chart, we can view cycle-time for the issues which are showing individually. However, if it's a cluster of issue and I need to view cycle-time for a particular issue in a cluster how to do it? I can filter using assignee; is it possible to search & view it by issue-key?

[Bill Sheboy · Accepted solution]

Hi @Vinay Sharma 

This is for a classic project, correct?  If so, for that chart you can select the filter from the available quick filters.  Try to create a quick filter for the board, and then use that to focus your view to the desired issues.

Best regards,

Bill

[Mariana_Pryshliak_Saasjet]

Hello @Vinay Sharma 

As an alternative solution, you can try both Time in Status for Jira Cloud and Time between Statuses.

Time in Status for Jira Cloud calculates how long an issue has been staying in each status. It also generates an Assignee time report, so you get info about a particular assignee easily.

Time between Statuses shows how long it takes an issue to move from one status to another. Also, it calculates Cycle time - actually what are you asking about.

So you can try and choose which one fits you the best.

Hope it helps.

Best regards, Mariana

[Emre Toptancı _OBSS_]

Hello @Vinay Sharma ,

The Control Chart which is available in Kanban Board reports, provides a high level solution. I think it is a little hard to work with since:

• Lack of control over reporting details
• Inability to work with individual issues or statuses
• Not being able to get the raw data

Even so, if might be enough if you just need a high level picture of things.

For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app. 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 or assigned to each assignee as well as entry/exit dates for all statuses. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype). You can also combine statuses into consolidated columns to see metrics like Age, Cycle Time or Lead Time.

 

The app calculates its reports using already existing Jira issue histories so you don't have to modify your workflows and when you install the app, you can get reports on your past issues as well.

The app has Custom calendar support which means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

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 issuetype.)
• Export your data as XLS, XLSX or CSV.
• Access data via REST API.
• Visualize data in various chart types.
• See Time in Status data under each issue in Time in Status tab.

Timepiece - Time in Status for Jira

EmreT