Is there a way I can get roll-up dates from Epic items into an export file or Confluence database?

[Karel van Leeuwe]

Is there a way I can get roll-up dates from Epic items into an export file or Confluence database?

Roll up dates on your timeline | Jira Cloud | Atlassian Support

We use epic items to track the progress of deployments in various factories. I would like to get insights into the total lead time (start date --> end/due date) for every deployment and have that into a format that can be exported (to excel for example) such that I can start tracking metrics like "average lead time per deployment" etc. 

I have made an overview into a Confluence database of all my epics, but in the database I can only get the start date + due date values of the epic if they are overridden into the epic itself, it does not show the roll up values.

[Danut M _StonikByte_]

Hi @Karel van Leeuwe,

Welcome to Atlassian Community. 

I'm afraid that is not possible by using the native Jira / Confluence native tools.

A possible solution would be to search for an app (plugin) on Atlassian Marketplace.    

If you consider the idea of using a plugin, our Great Gadgets app offers all you need for tracking the lead time of your deployments in an effective manner. 

Control Chart - can display your completed deployments by their lead time. It displays the average and helps you easily identify the outliers and the ones that took longer than expected (by setting a threshold)

Trend Chart - can the average lead time of your deployments per past time intervals and the overall average. It helps you see if the lead time improves in time, form a week to another or from a month to another

Histogram Chart - shows the distribution of lead time your deployments and how many took longer than expected

WIP Aging Chart - shows the age (since creation) of your active deployments

All these gadgets can display a Data tab with details info for each issue, which you can easily export in CSV:

How to configure these gadgets for your use case?

• as Data source use a JQL or filter that returns the epics that represent the deployments
• Cycle stats: Since issue creation and Cycle ends: When the issue entered a status that has category "Done"

The gadgets do not use a Due field, but they can measure until the epic (deployments) reached a done status.

If you need any help with the setup, feel free to contact us at support@stonikbyte.com.

Danut. 

[Laura Campbell]

Hi @Karel van Leeuwe and welcome to Community!

Could you explain a bit more what you are trying to achieve? That will help Community members better identify a good solution for you.

Since you mention a Confluence database, are you trying to track work items from Confluence? 

[Karel van Leeuwe]

Hi Laura, absolutely! We use epic items to track the progress of deployments in various factories. I would like to get insights into the total lead time (start date --> end/due date) for every deployment. In my original post I added images. I am using Jira to track epics, but I am using a Confluence database to get consolidated overviews. Let me know if you need more information.