briancunning added a comment - 02/Oct/2020 9:23 AM
People have been crying out for this for years. The opportunity to unlock a huge amount of value for it's users is being missed. The control chart is nice and all but it hides information, especially when it groups issues that were resolved on the same day.

You can hack the data from the table in Chrome by right clicking on the table, clicking Inspect. This should open up the developer tool on the righthand side. Click on the Network tab. Refresh the page. This lists all the data elements retrieved on the left hand side of the developer tools window. Scroll down to controlChart.json and you should be able to view it's contents on the preview pane on the right.

I've been able to copy this data into software that can format the Json such as Notepad ++ and extract the information I need but it is painful.

After you copy the contents of the json, do the following:

1) Open https://www.db-fiddle.com/

2) Choose Postgres 15 as a database.

3) In Schema SQL put this:

Create table chart as select  $$ 
-- put your json here.
$$::json 

IMPORTANT! I don't know if db-fiddle saves the data that it processes. You have ticket keys and summaries within that json, so be aware of that

4) Then in Query SQL put this:

with fieldnames as 
(
  select json_array_elements(json -> 'columns')->> 'name' as name from chart
),
fields as (
  select row_number() over () as number, name from fieldnames
),
issuesjson as (
  select json_array_elements(json -> 'issues') as issue from chart
),
issuesflat as (
  select issue ->> 'key' as key,
         json_array_elements_text(issue -> 'totalTime')::numeric as totalTime,
         json_array_elements_text(issue -> 'workingTime')::numeric as workingTime,
         json_array_elements_text(issue -> 'leaveTimes')::numeric as leaveTime
  from issuesjson
),


issues as (
  select *,
         row_number() over (partition by key) as number
  from issuesflat
)


select i.key as "Key", 
       f.name as "Status",
       round(i.totaltime / 60 / 60 / 1000,3) as "Total Time, Hours",
       round(i.workingtime / 60 / 60 / 1000,3) as "Working Time, Hours",
       coalesce(TO_CHAR(to_timestamp(nullif(i.leavetime,-1) / 1000), 'YYYY-MM-DD HH:MI:SS'),'') as "Last Leave Time"
  from issues i
  join fields f on f.number = i.number


order by i.key, i.number 

5) Click "Run"

6) Then open your DevTools/Inspector and find the table tag

7) Copy its contents as HTML

8) Paste it to MS Excel On your Desktop

Please enable this feature! I beg you Atlassian!

+1

+1

+1

+1

+1

+1

+1

+1

I vote for this issue to fix

+1

+1

+1

Well i watched this request for almost 9 years but it's probably time to accept that they'll just never do it

+1

Exactly, I know the reason, it is to allow other plugins to thrive on the platform and not to implement features that are available on the Jira market, but after trying a few, all suck, and none of them gives the information in an easily consumable way.

I think the benefit for customers outweighs the upsetting of plugin devs, the plugin devs have got more than enough notice to do something more innovative rather than implementing a feature that I think is essential to Jira.

Please consider including this ASAP.

I agree with @Brian, I did exactly the same, and almost written some code to extract the details from JSON, but didn't feel worth it, especially that you need to get the information manually from Chrom inspect.

This ticket has been here for more than 8 years!!!

People have been crying out for this for years. The opportunity to unlock a huge amount of value for it's users is being missed. The control chart is nice and all but it hides information, especially when it groups issues that were resolved on the same day.

You can hack the data from the table in Chrome by right clicking on the table, clicking Inspect. This should open up the developer tool on the righthand side. Click on the Network tab. Refresh the page. This lists all the data elements retrieved on the left hand side of the developer tools window. Scroll down to controlChart.json and you should be able to view it's contents on the preview pane on the right.

I've been able to copy this data into software that can format the Json such as Notepad ++ and extract the information I need but it is painful.

We need this feature. We should be able to publish this data for management.

+1

+ 1 for this feature

Working on custom solution from this using back end data. Life would be much easier if the control report provided exports of this data for manipulation. 

Hi!, we need this feature too. Currently exporting cycle time data it's a tedious manual task

How is that this is yet to be implemented!!!??? It's basic stuff. 

Please hurry on this!

Yes, ability to export and analyze issue cycle time is very important to our practice.

Definitely require a JQL filter that can allow us to easily calculate and export Cycle time data. Currently it's a tedious manual process.

Me too.

I have 5 teams, each having a board.  I'd like to be able to write some sort of query where I could specify the board ID, and get Lead & Cycle Time.

The reason why I'd like to specify the Board ID, is, we have multiple teams all sharing the same Jira project.  Each board has a filter where only the tickets with the Team component display on that team's board.  E.g. Component = AEM, it appears on the AEM team's board.  I only care about the issues which have been on the AEM team board.  Actually, I guess I could do this by simply specifying "Component = AEM" in the Cycle Time query, and not bothering with the board ID...  so yeah, forget the board ID suggestion.  The only thing which matters is all issues matching a JQL filter, and their time in certain statuses.  From that, it would be easy to calculate Lead and Cycle time.

This would be a huge benefit to my team as we review a 3 sprint rotation of cycle time to see trends and determine is changes we made to improve our process are having the expected impact on our cycle time. The problem is that we have to go into Jira to see the data and then open issues in a new tab to review the work and discuss especially for the outliers. It would be much easier if we had access to the underlining data and can export that to Excel or other tools to view the data. I really hope this get traction.

Stunned that this is not already part of the core product. 

Please consider making this available.

Would love to see this feature as digging into cycle time is imperative on the road to high-performing teams. Please please provide an easy way to dig into cycle time better!

+1 Would certainly help teams in a retrospective, being able to quickly filter say the top 3 outliners in the sprint would be very valuable to help support continuous improvement. 

@matt nodder, absolutely, a JQL function on the line of:

cycleTime(list_of_statuses), for example:

cycleTime('In Progress','Ready for Release')

This would be great.

The control chart is a very valuable tool to analyse outliers, helping teams improve estimating/planning and improve their overall efficiency. Being able able to export this data into excel or at least have cycle time as a valid JQL value would be fantastic. Please add this as a feature! Thanks

An internet search for Export Cycle Time in Jira is littered with people requesting this for years.

There are loads of plugins that seek to fill this gap. Not everyone has the ability to install these plugins.

It is a basic function of Kanban to know the Lead times for each status in your workflow.

The control chart display this information in a nice way but you have to hover over individual tickets to see the lead times.

A table view or an export function would solve this problem. 

An option to view all issues in issue navigator would be a nice start.

Please add this feature. It will help a lot of your customers and will really be useful to have cycle time and time spent in each column. I can see that by hovering over the issues in control chart and clicking on it that you have the data captured that each issue spends in various columns so please make it available for export.

+1 for this feature

+1 for this feature, and also to add the underlying data as fields from JQL.

+ 1 for this feature

+ 1 for this feature

+1 for this feature 

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature 

+1 for this feature

+1 for this feature

+1 for this feature

+ 1 for this feature
 

+ 1 for this feature

+ 1 for this feature

+ 1 for this feature

+ 1 for this feature

+ 1 for this feature

+ 1 for this feature