Want to track Devops metrics in Dashboard

[IT]

1. Deployment frequency 2.Lead time for changes 

3.Change in failure rate 4. Mean time to recover 

I want to track all this metrics in Dashboard. 

[Emre Toptancı _OBSS_]

Hello,

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. I can recommend our app for your need number 2 and 4. It is available for Jira Server, Cloud, and Data Center.  

(I presumed service recovery times are also measured through issue statuses. If not, we would like to hear the specifics of your case as well)

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. 

       

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. This report type has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user the exclude the times for "pause" statuses.

  

All Time in Status reports supports custom calendars. That means you can define your custom work calendars with their own working days and working hours. Time in Status will calculate durations only spent in those calendar hours.

These reports show a list of issues by default so you can see the metric values for each issue separately. Also, for all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total cycle time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

Time in Status 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. It supports both Company Managed and Team Managed projects.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

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.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• 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

Timepiece - Time in Status for Jira

EmreT

[Meghan LaClair]

Disclaimer: marketplace partner

Hey @IT -There are a ton of services that offer DORA dashboards - I would be curious to learn more about why you are interested in them?

The reason I ask is DORA metrics seem to be trending and they are only worth optimizing if they are truly the bottleneck (weakest link in the engineering value chain). For example you can optimize deployment frequency to the point the team is deploying hundreds of times per day but if the results aren't tied to business outcomes you are going to run into frustration across the board instead of results.

A tool like minware provides a global view of engineering activity that can expose dependencies not picked up by metrics like DORA - think: "How much distraction-free time does the team have to work on customer projects in the first place?" - seems very basic and simple, because it is, but it's a question DORA metrics can't answer.

Let me know if you'd like to check it out! 

[IT]

Thanks @Meghan LaClair 

Actually I want to track Deployment frequency. 

Yes,I'm interested to check about Dora

and services that offer Dora dashboard.