> 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-march-2022-updates.md).

# Oobeya March 2022 Updates

## Summary

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

* [x] \[BETA] Deployment Analytics (DA) - [DORA Metrics](https://oobeya.io/dora-metrics/)
* [x] DA - Jenkins Integration
* [x] DA - Git Release Integration
* [x] DA - Team Goals
* [x] DA - Automated Reanalyze
* [x] DA - Time Period Comparison
* [x] DA - Deploy Size
* [x] DA - [DORA Metrics](https://oobeya.io/dora-metrics/) on Team Scorecards
* [x] Gitwiser Active Analytics Types
* [x] AgileSpace Reset Analysis
* [x] Download System Logs

## :beginner: \[BETA] Deployment Analytics (DORA Metrics)&#x20;

Calculating [DORA metrics](https://oobeya.io/dora-metrics/) is not easy. We're still working on the Deployment Analytics module so that teams can effortlessly track accurate [DORA metrics](https://oobeya.io/dora-metrics/) calculated by Oobeya.

<details>

<summary>Best tool to track DORA metrics: <strong>Why Oobeya Deployment Analytics?</strong></summary>

* Proven Metrics ([DevOps Research & Assessment](https://www.devops-research.com/))
* Quick Start (Measuring DORA metrics [has never been easier](https://www.youtube.com/watch?v=EYE4e1gTs80))
* Cross-Platform Analysis (SCM x CI/CD x APM)
* Accurate Results :white\_check\_mark:

**Discover DORA Metrics** with Oobeya: [https://oobeya.io/dora-metrics](https://oobeya.io/dora-metrics/)

</details>

{% hint style="info" %}
***Oobeya Deployment Analytics*** works with [GitLab CI](/integrations/all-integrations/scm-addons/gitlab-addon.md), [AzureDevOps](/integrations/all-integrations/scm-addons/azure-devops-integration.md), [Jenkins](/integrations/all-integrations/scm-addons/jenkins-integration.md) for now.&#x20;

Coming soon: *GitHub Actions, Spinnaker, BB Pipelines, Octopus,* and more...
{% endhint %}

## :electric\_plug: New Integrations

#### 1- Deployment Analytics (DORA metrics) - Jenkins Integration

Oobeya Deployment Analytics now works with [Jenkins](/integrations/all-integrations/scm-addons/jenkins-integration.md). If you have a **\[Git Repo X Jenkins]** pipeline configured, you can calculate [DORA metrics](https://oobeya.io/dora-metrics/) by using Oobeya.

![GitLab-GitHub-Bitbucket-AzureDevOps X Jenkins](/files/x3RvydnKk3jdcOntMLQN)

#### 2- Deployment Analytics (DORA metrics) - Git Release

**Calculate DORA metrics without pipeline configuration (Git Release)**

Oobeya Deployment Analytics now works without any CI/CD pipeline integration. You can calculate DORA metrics just by selecting the git branch your team released.

![Select the git branch your team released](/files/t9dBkQLY2aPFmGpReDGg)

## :gift: New **Features**

#### **1-** Deployment Analytics - **Team Goals**

You can set your organizations' default goals for each stage of the "Lead Time For Changes" breakdown.

![Deployment Analytics default goals - Admin Panel](/files/RTm7gJQrx9714y9hAR29)

Oobeya checks these goals and displays warnings on the deployment flow to show you where you may improve.

![Lead Time For Changes breakdown - where you may improve.](/files/loaYpKmm95vZ3Ntv1z9E)

#### **2-** Deployment Analytics - **Automated Reanalyze**

We've added new functionality for Deployment Analtyics (BETA): Automated Reanalyze is now ready to use!

#### **3-** Deployment Analytics - **Time Period Comparison**

To track the changes in [DORA metrics](https://oobeya.io/dora-metrics/), we've added a time period comparison: *"Last week" vs. "Previous week".*

!["Last 6 months" vs. "Previous 6 months" ](/files/CoF4BfwWpUrg48FFFKSA)

#### **4-** Deployment Analytics - **Deploy Size**

We've started to show the size of each deployment pipeline: *Small, Medium, Large, Gigantic.*

![Deploy Size](/files/WHzxc86fHNdLkAvukXmi)

#### **5-** DORA Metrics on Team Scorecards

Oobeya [Team Scorecards](/team-health/team-scorecards.md) now display [DORA Metrics](https://oobeya.io/dora-metrics/), allowing you to track and improve metrics (Lead Time For Changes, Deployment Frequency) at the team level.

#### 6- Gitwiser - Active Analytics Types

On Gitwiser's home page, we've started to show active analytics types for repositories. You can now navigate to the analysis results with ease.

![Gitwiser Active Analytics Types](/files/91sGNzdfMEnDgvqrIjtU)

#### 7- AgileSpace - Reset Analysis Button

You can now reset your existing [AgileSpace Board Analytics](/project-analytics/project-analytics-metric-definitions.md) reports via the "Reset Analysis" button. After clicking the button, all history will be removed, but your settings and configuration will be preserved.

![Oobeya AgileSpace Reset Board Analysis](/files/YmoUQOBsujMtWWjb1Tpg)

#### 8- Administration - Download System Logs

Now you can download system logs from the administration panel.

![System Logs](/files/6p8Cj3aiVLLTEnibVsYA)


---

# 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-march-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.
