Average release time in a dashboard ?

[Corinne Guibert]

Hello

I got this request from a user and I'm not sure if this is possible to  have it in a dashboard.

He is managing a project with Release and he asked me if it's possible to track the average duration (time between start date and  release date) of the Releases in his project.

Ideally to be added in his current Jira dashboard

Is it possible ? If not, how we could do it ?

Thanks for your feedbacks

[Rahul_RVS]

Hi @Corinne Guibert 

As suggested by everyeone, you will need a mktplace app for these requirements. If you would like to try out one, pls explore

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. It works for current issues and closed ones as well.

With Status grouping feature, can help you define your own cycle time / issue age time and view the averages of the same. Also the app has 20+ reports to meet a variety of use cases.

You can set your own working calendar to exclude weekends and holidays from the time in status calculation.

The app can be easily added as a dashboard gadget and can be shared with colleagues.

More details here.

Disclaimer : I am part of the app team for this add-on 

[Birkan Yildiz _OBSS_]

Hey @Corinne Guibert

Native Jira dashboard gadgets are great for high-level overviews, but they don't natively calculate the average duration between two specific date fields to display as a dashboard metric. If you are open to using a Marketplace app, you can easily build this exact view using Timepiece - Time in Status for Jira.

Here is how you can set it up for your user:

Define the Exact Duration: Use the Duration Between Statuses report. Instead of using workflow statuses, you can set the Start At metric to your "Start Date" field and the Stop At metric to your "Release Date" field. This calculates the exact time elapsed between those two specific dates.

Get the Average per Release: Change the report option from a standard list to an Average report.

You can then use the "Group By" option and select your Release field (like "Fix Version"). This will automatically calculate and display the average duration for each specific release.

Add to the Dashboard: Timepiece includes a dedicated Dashboard Gadget. You can place this exact average report directly onto his current Jira dashboard, and even visualize the data using bar or column charts for a quick executive view.

Pro tip: You can also configure the gadget to use Custom Calendars. This ensures the calculated duration only reflects your actual business hours, automatically excluding weekends and holidays from the average release time.

Hope this helps. You can visit Timepiece’s Atlassian Marketplace page. Please do not hesitate to contact me if you have any further questions.

Disclosure: I am part of the OBSS team, the creators of Timepiece.

Best,
Birkan

[Anastasiia Maliei SaaSJet]

Hi, @Corinne Guibert 

Native Jira dashboard gadgets don’t provide a built-in way to calculate and display the average duration between release start date and release date.

However, this can be covered with a Marketplace app like Time Metrics Tracker | Time Between Statuses.

With the app, you can configure a custom duration metric for the needed period — for example, from the release start point to the release/completed point.

Then, using the Agile Metrics Gadget, you can display this metric directly on the Jira dashboard, including its average value.

So the setup would be:

1. Create a custom metric, for example Release Duration.
2. Define the start and end points of the metric.
3. Select the needed project and issue scope.
4. Add the Agile Metrics Gadget to the Jira dashboard.
5. Show the metric as an average duration.

[Maria Reisinger]

Great question and more common than you'd think.

The short answer: Jira can't do this natively.
Jira tracks releases beautifully but it's a work management tool, not an analytics engine. It stores the start date and release date, but it doesn't automatically calculate the delta between them, and it definitely doesn't average that delta across all releases and surface it in a dashboard gadget.

The best native workaround:
Create a numeric custom field called something like "Release Duration (days)". Then set up an automation rule that fires when a version is released, calculates the difference between start date and release date, and writes that number into the field. Once you have that field populated historically, you can use a dashboard gadget to show averages.
It works, but it's manual setup and it still won't tell you why a release took longer than usual, or whether your cycle time is trending up or down.

The deeper question:
What your user is really asking is: "Is our release process healthy and is it getting better or worse?" That's not a dashboard gadget problem, that's an operational intelligence problem. The data is all in Jira. It just never surfaces automatically.

That's exactly what we're building at MetaFrazo: operational signals that sit on top of Jira metadata and surface things like release cycle time trends automatically, without anyone having to build custom dashboards or run manual queries. We're launching this summer on the Atlassian Marketplace and are currently looking for 20 beta customers starting June. If that sounds interesting, happy to share more.

[Bill Sheboy]

Hi @Maria Reisinger -- Welcome to the Atlassian Community!

What is the source of the content you posted?

As a reminder, posting completely "AI" generated content is not permitted per the community rules of engagement / guidelines.  And, when using such tools to alter content, please disclose that usage in the post text.

To learn more, please see:

https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement

Kind regards,
Bill