Epic Cycle Time fields and calculation

Question

Hi, We are looking to calculate Epic cycle time using the control chart and would like to find out what exact fields the chart uses to calculate the cycle time.  We would be looking to calculating from in-progress to done.

Also, it is possible to expose these fields so they can be editable, so we can correct data if we find ones that have incorrect dates?

Yuliia_Borivets__SaaSJet_ · Answer

Hi @Bret Spangenberg

Agree with Bill on editing the measurements. Controlling issues on board can be uneasy.

If you need to calculate time from in-progress to done, try Time in Status for Jira Cloud developed by my team. You can generate time in status report with cycle and lead time here.

A short guide on how to configure time cycle:
1. Open columns manager
2. Choose Add New Group in Status Groups menu
3. Add a name and statuses you need, and save.
4. Save the column to display it.

Check out how it works with online demo.

Hope it helps.

Regards

Mehmet A _Bloompeak_ · Answer

Hi @Bret Spangenberg ,

As an alternative, you can try Status Time app developed by our team at Bloompeak. It provides reports on how much time passed in each status as well as status entry dates and status transition count.

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. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project). And all these are available as gadgets on the dashboard too.

Here is the online demo link, you can see it in action and try.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

Emre Toptancı [OBSS] · Answer

Hello @Bret Spangenberg ,

Control chart is prepared based on issue history records (which you can see in History tab of each issue's view screen) and editing them is not possible. I should also note that control chart is very limited in terms of flexibility. It draws the overall picture but does not give you a lot of details.

For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine statuses in any way into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the total InProgress time per Epic, or average resolution time per issuetype).

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.

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. Sort and Filter according to report values.
* 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. (for integrations)
* Visualize data with various chart types.
* See Time in Status reports on Jira Dashboard gadgets (released for cloud, server&DC gadget coming soon)

Timepiece - Time in Status for Jira

EmreT