> For the complete documentation index, see [llms.txt](https://docs.oobeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oobeya.io/product/release-notes/oobeya-feb-2022-updates.md).

# Oobeya Feb 2022 Updates

:tada: We are excited to introduce our new features and improvements.

### \[BETA] Deployment Analytics (DORA Metrics) 

We have started developing the "Deployment Analytics" feature to evaluate [DORA metrics](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance) (Four key metrics).

For the BETA release, you can now calculate two of the DORA metrics for your deployments:

1. **Deployment Frequency**—How often an organization successfully releases to production
2. **Lead Time for Changes**—The amount of time it takes a commit to get into production

![Deployment Analytics (DORA metrics)](/files/b9HdDTEhI9PrfoHwaHrF)

![Deployments during the selected period (with details and breakdown)](/files/JOQ0a7eFnwYbW68D0Tgh)

What we deliver in the BETA release:

* Lead Time For Changes (Breakdown)
* Lead Time For Changes (Average)
* Deployment Frequency (Deployments/day)
* Deployment Frequency (Historical chart)
* Deployments during the selected period (with details and breakdown)

{% hint style="info" %}
***Deployment Analytics*** works with [GitLab CI](/integrations/all-integrations/scm-addons/gitlab-addon.md) and [AzureDevOps ](/integrations/all-integrations/scm-addons/azure-devops-integration.md)for now. (Coming soon: *Jenkins, GitHub Actions, Spinnaker, BB Pipelines, Octopus,* and more...) 
{% endhint %}

With the developments we have done so far, you are able to define your own cross-platform delivery cycle configuration. Then, we will take forward the other DORA metrics (Change Failure Rate and Time to Restore Service) by expanding this configuration with different tools such as incident management (PagerDuty, OpsGenie), change management (ServiceNow, Jira), and APM (NewRelic, Sentry, Dynatrace, etc.) tools.

![Initialize a new Gitwiser Analysis](/files/i4AwIlzWgMdIrpxaMgsa)

### Gitwiser

#### Excluded Commits Table

In [Gitwiser ](/gitwiser-repo-analytics/git-analytics-metric-definitions.md)you can now see all the excluded commits along with the exclusion reasons in a table. You also are able to include them in the analysis.

![Gitwiser Excluded Commits Table](/files/l5dOlAltqGMpaLPwjLFu)

### Dashboards

#### Duplicate Dashboards

Now you can effortlessly duplicate your dashboards by using the "Copy From" option.

![Duplicate your dashboards](/files/0ljU9gqZQXQkk5STr0wV)

#### Sonarqube Unit Tests Widget

We have added a new pre-defined [widget](/dashboards/adding-a-new-widget.md) for [Sonarqube ](/integrations/all-integrations/code-quality-addons/sonarqube-integration.md)addon to show the unit test results of your projects in [Oobeya Dashboards](/dashboards/creating-a-new-dashboard.md).

![Sonarqube Unit Tests Widget](/files/sMSaKy8DgtgHtRbLapmC)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.oobeya.io/product/release-notes/oobeya-feb-2022-updates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.