We have generated a cycle time report for a large number of projects and tickets. It has an odd gap

[Sharon Robinson]

We have generated a cycle time report for a large number of projects and tickets. It has an odd gap in the graph that doesn't seem to exist in the data. 

Can anyone explain why this might be?

Screenshot of graph:

With the gap circled:

[Ayça Erdem_OBSS_]

Hello @Sharon Robinson 

Welcome to the community 

If you're seeing an unexpected gap in your cycle time trend chart especially when working with a large dataset across many projects I would recommend trying Timepiece - Time in Status for Jira, developed by our team at OBSS. It allows you to explore these kinds of gaps in a clear and non-complicated way, without scripting or workflow changes.

The Duration Between Statuses (DBS) Report in Timepiece lets you calculate Cycle Time using the Metric button, you can first define your Cycle Time  for example, from “To do” to “Done”.

When you click the Drill Down button, you'll see the list of issues included in the related filter.

In the screenshot above, the Duration Between Statuses report displays the average cycle time grouped by created week.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. 

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.

If you'd like to explore this solution further, feel free to check out Timepiece - Time in Status for Jiraon the Atlassian Marketplace.

Hope it helps

Ayça

[Danut M _StonikByte_]

Hi @Sharon Robinson,

I think it's just the way that chart displays the data. It's expanding the areas where there are many issues for better visualization (look at the distance between 0 and 20 on y axis). So a feature, not a bug. And that gap is because your issues do not fit that area. But you could eventually open a ticket with Atlassian Support to get this clarified.

Alternatively, you could try a plugin from Atlassian Marketplace that offers such a report or gadget to compare the data. In case you consider the idea of using a plugin, our Great Gadgets app offers a Control Chart gadget that you could try.

It is highly configurable and it can display a logarithmic vertical scale, for better visualization. 

Danut   

[Bill Sheboy]

Hi @Sharon Robinson -- Welcome to the Atlassian Community!

In my opinion, problems with Atlassian's interpretation of a control chart are difficult to diagnose due to the way it displays data and alters the axis scaling.  Regardless of that...

I did a quick check of the public backlog and do not see this symptom noted as a defect.  Perhaps this is an artifact in the chart for the way it scales the y-axis.

If you look closely, there are values in that elapsed time frame for your chart, which appears to be around 7 days.  Have you tried exporting the selected data for the current week to identify any issues which should have that amount and do not display?

What are the chart setting selections (below the images you show)?  Have you tried adjusting the settings to confirm if the issues are missing...or if there is some aspect of your process where few issues have that elapsed time?

Kind regards,
Bill