Oobeya Docs
  • GETTING STARTED
    • Welcome to Oobeya!
    • Get Started with Oobeya
    • Playground: Live Demo
    • Oobeya Quick Onboarding Guide
  • TEAM INSIGHTS & SYMPTOMS
    • Symptoms Catalog
      • S1- Recurring high rework rate
      • S2- Recurring high cognitive load
      • S3- High weekend activity
      • S4 - High Code Review Time
      • S6- High technical debt on Sonar
      • S7- High vulnerabilities on Sonar
      • S8- High code quality bugs on Sonar
      • S9 - Unreviewed Pull Requests
      • S10 - Lightning Pull Requests
      • S11 - Oversize Pull Requests
      • S12- High Lead Time For Changes (DORA)
      • S13- Low Deployment Frequency (DORA)
      • S14- High Change Failure Rate (DORA)
  • SECURITY
    • 🔐Security at Oobeya
    • Oobeya Managed SaaS
  • INSTALLATION
    • 🐳Oobeya Docker Installation Tutorial & Requirements
    • 🐳Oobeya Version Upgrade For the docker-compose Installations
    • 🐳HTTPS Configuration For Docker Installations
  • PRODUCT DOCS
    • ⭐Oobeya Release Notes
      • 🎁Oobeya 2024 Q1 - Release Notes
      • 🎁Oobeya 2023 Q4 - Release Notes
      • 🎁Oobeya 2023 Q3 - Release Notes
      • 🎁Oobeya 2023 Q2 - Release Notes
      • 🎁Oobeya 2023 Q1 - Release Notes
      • 🎁Oobeya Nov & Dec '22 Updates
      • 🎁Oobeya September 2022 Updates
      • 🎁Oobeya August 2022 Updates
      • 🎁Oobeya July 2022 Updates
      • 🎁Oobeya June 2022 Updates
      • 🎁Oobeya Apr & May 2022 Updates
      • 🎁Oobeya March 2022 Updates
      • 🎁Oobeya Feb 2022 Updates
      • 🎁Oobeya Jan 2022 Updates
      • OOBEYA-2.0.8 - Release Notes
      • OOBEYA-2.0.4 - Release Notes
      • OOBEYA-2.0.0
      • OOBEYA-1.4.6
      • QAD-1.0 - 1.4
    • ▶️Product Tour
    • ❇️Metrics List
    • ☀️Developer Experience Metrics
  • INTEGRATIONS
    • Integration Catalog
      • SCM & CI/CD Integrations
        • Azure DevOps Integration
        • Bitbucket Cloud Integration
        • Bitbucket Server Integration
        • GitHub Integration
        • Step-by-Step Integration Instructions for the Oobeya GitHub Application
        • GitLab Integration
        • Jenkins & Cloudbees Integration
        • Octopus Deploy Integration
        • TeamCity Integration
      • Quality & Security Integrations
        • SonarQube Integration
        • SonarQube Cloud Integration
        • Veracode Integration
      • Project Management Integrations
        • Jira Cloud Integration
        • Jira Server Integration
      • APM / Monitoring Integrations
        • AppDynamics Integration
        • Azure Application Insights Integration
        • Dynatrace Integration
        • Elastic APM Integration
        • New Relic Integration
        • Sentry Integration
    • Installing An Addon
    • Adding A New Data Source
    • Updating and Deleting Data Sources
  • ADMINISTRATION
    • User Management, Single Sign-On, Auth Settings
      • Microsoft Entra (Azure AD) Integration
      • LDAP / Active Directory Integration
      • Importing a New User From LDAP / Active Directory
      • Bulk User Import in Oobeya Using CSV
      • Adding a New User
      • Deactivating a User
      • Understanding Roles in Oobeya
    • License Management
      • Updating The License Key
  • DEVELOPMENT ANALYTICS - GITWISER
    • Git Analytics - Metric Definitions
      • Coding Impact Score
      • Impact Ratio (team-level)
    • Setting Up Development Analytics And DORA Metrics
    • Git Analytics Exclusions
    • Setting Automated Reanalyze For Gitwiser
    • Deployment Analytics (DORA Metrics)
    • Merging Contributor Accounts
  • DORA Metrics
    • DORA Metrics Introduction
      • Lead Time For Changes (LTC)
      • Deployment Frequency (DF)
      • Change Failure Rate (CFR)
      • Mean Time To Restore Service (MTTR)
    • Failure Detection (For Change Failure Rate & MTTR)
    • How To Calculate DORA Metrics for GitHub
    • Updating Team Scorecard configuration to display DORA Metrics
    • How To Start Deployment Analytics (DORA Metrics) For An Existing Gitwiser Analysis
  • Project Analytics - AgileSpace
    • Agile Analytics - Metric Definitions
    • Agile Board Analytics Intro
    • Starting an Agile Board Analytics
    • Board Overview
    • Sprint Reports
    • Update the Agile Board Analytics
  • QUALITY ANALYTICS
    • Total Code Quality Index (TCQI)
  • Guides
    • Azure DevOps Guides
      • How To Calculate DORA Metrics for Azure DevOps
      • Best practices for integrating Oobeya with Azure DevOps Scrum Boards
  • PROFILES
    • Introduction
    • Adding A Profile
    • Developer Scorecard
    • Adding A Related Account Information To Oobeya Profile
  • Team Health
    • Adding A Team
    • Team Scorecard
    • Project Analytics (Scrum Teams) Widget
  • Test Quality Report Widget
  • CUSTOM DASHBOARDS
    • Adding A New Dashboard
    • Adding A New Widget
    • Updating And Deleting Widgets
    • Adding Jira Sprint Progress Widget
    • Adding Jira Board Metrics Widget (Metrics With JQL)
  • SUPPORT
    • Support Request Workflow
    • Customer Success & Support Guide
Powered by GitBook
On this page
  • ​🎁 NEW FEATURES - TOP 10
  • #1 Oobeya Team Health [BETA] - Autodetected Symptoms
  • #2 Bulk User Import From LDAP
  • #3 LDAP User Sync Button
  • #4 Oobeya OKTA Integration
  • #5 Oobeya Veracode Integration
  • #6 Tracking New Relic Incidents to Detect Production Failures Automatically for DORA Metrics Calculation
  • #7 Identifying Hotfix Naming Patterns to Detect Production Failures Automatically for DORA Metrics Calculation
  • #8 DORA Metrics Trends In A Timeline View
  • #9 Identifying Reverts and Calculating Pull Request Revert Rate
  • #10 Individual Scorecards Feature on/off Toggle
  • IMPROVEMENTS
  • SEE OOBEYA IN ACTION!

Was this helpful?

  1. PRODUCT DOCS
  2. Oobeya Release Notes

Oobeya 2023 Q1 - Release Notes

Check out the new features and improvements we've released for you.

PreviousOobeya 2023 Q2 - Release NotesNextOobeya Nov & Dec '22 Updates

Last updated 1 year ago

Was this helpful?

We are super excited to share our new features and improvements with you!

​🎁 NEW FEATURES - TOP 10

  1. to Detect Production Failures Automatically for DORA Metrics Calculation

  2. to Detect Production Failures Automatically for DORA Metrics Calculation

#1 Oobeya Team Health [BETA] - Autodetected Symptoms

The module is a powerful tool for detecting and addressing problems in software development and delivery processes. By collecting and analyzing data from a variety of sources, the module is able to identify and alert teams to issues such as recurring anti-patterns, bad practices, and bottlenecks.

The Oobeya Symptoms module includes the following features:

  • Identification of patterns and trends that may indicate problems or inefficiencies

  • Recommendations for addressing detected issues

No #
Smyptom
Symptom Source

S1

Gitwiser - Git Analytics (VCS tools)

S2

Gitwiser - Git Analytics (VCS tools)

S3

Gitwiser - Git Analytics (VCS tools)

S6

Sonar

S7

Sonar

S8

Sonar

S9

Gitwiser - PR Analytics (VCS tools)

S10

Gitwiser - PR Analytics (VCS tools)

S11

Gitwiser - PR Analytics (VCS tools)

Oobeya Symptom Catalog

Each symptom includes a description, potential complications, possible causes, improvement areas, and a detection method.

#2 Bulk User Import From LDAP

As an enterprise-grade solution, we understand the importance of providing users with a seamless experience. No matter your organization's size, we know that managing users can be a cumbersome and time-consuming process. That's why we are excited to introduce our new LDAP Bulk User Import feature to manage users easier and faster.

The LDAP Bulk User Import feature allows users to quickly import large groups of users into their Oobeya account. This saves time and makes it easier to keep your user base up-to-date. This feature also ensures that user accounts are secure and compliant with your organizational protocols.

We hope this feature provides our customers with an improved user experience and helps to reduce the time needed to onboard new users. We are committed to continuing to improve Oobeya and provide our customers with the best possible user experience.

If you have any questions about using LDAP Bulk User Import, please reach out to us and one of our team members will be happy to help.

#3 LDAP User Sync Button

The LDAP User Sync button and functionality allow you to quickly and easily synchronize your user list with your LDAP directory. This means that when a user is deleted from the LDAP directory, her/his account will be deleted (deactivated) from Oobeya automatically. This helps ensure that only valid users have access to your Oobeya system, improving security and reducing the time it takes to maintain your user list.

The best part is that the LDAP User Sync button can be scheduled to run automatically, so you don’t have to worry about manually updating your user list. This is a great time saver for busy administrators and teams.

We hope you enjoy the new LDAP User Sync feature and find it helpful in keeping your user list up-to-date and secure. As always, if you have any questions or feedback, please don’t hesitate to contact us.

#4 Oobeya OKTA Integration

We’re pleased to announce that Oobeya is now integrated with OKTA! This new feature makes it easier for OKTA users to manage user identity, access, and authentication.

In addition to the improved security, the integration with OKTA streamlines the user experience. With OKTA, users can access Oobeya as other applications with one click. This makes it easier than ever to access the Oobeya platform and manage user identity and authentication.

If you have any questions or need help getting started, don't hesitate to contact our support team.

#5 Oobeya Veracode Integration

The new integration will provide Oobeya customers with enhanced visibility into their application security posture, allowing them to identify and address security risks quickly and effectively. It will also enable customers to streamline their application security processes.

We understand the importance of security and are committed to helping our customers stay ahead of the threats posed by malicious actors. The Veracode integration is the latest step we’re taking to ensure that our customers have the best tools available to protect their applications.

Oobeya Team Health & Veracode integration

With Oobeya, engineering leaders can get valuable insights into their development teams and improve the developer experience and team health. The Team Health module is designed to address both technical and cultural aspects of the development and delivery processes, providing a holistic approach to optimizing team performance in software development.

The Team Health module is comprised of two main components: Team Symptoms and Team Scorecard. Team Symptoms provides a visual representation of team health, highlighting potential areas for improvement and addressing the root causes of team dysfunctions. Team Scorecard, on the other hand, provides a quantitative assessment of team performance, measuring key metrics such as lead time, code review, code quality, and DORA metrics. Now, + Veracode security metrics!

#6 Tracking New Relic Incidents to Detect Production Failures Automatically for DORA Metrics Calculation

With Oobeya, you can now connect and track New Relic incidents to detect production failures automatically and more accurately calculate your DORA Metrics, such as the Change Failure Rate (CFR) and Mean Time To Restore Service (MTTR). This new feature helps streamline the process of measuring your DORA Metrics, saving you time and effort.

To get started, simply connect your New Relic account to Oobeya, select your New Relic application in the Gitwiser Deployments (DORA) behind your repository + CICD pipeline, and the rest is taken care of automatically.

#7 Identifying Hotfix Naming Patterns to Detect Production Failures Automatically for DORA Metrics Calculation

Oobeya can now identify hotfix naming patterns to detect production failures automatically for DORA metrics. With this update, Oobeya can now automatically detect production failures by analyzing your git branch naming conventions.

To identify hotfix deployments, Oobeya looks for naming patterns in the branch name, Pull Request title, and deployment title. Because hotfix deployments are used to fix critical production issues, Oobeya sets the health status of previous deployments to Failure.

This new feature provides teams with an efficient and automated way of tracking their CFR, as well as other DORA metrics.

#8 DORA Metrics Trends In A Timeline View

With this new feature, you can now view and compare your team’s performance over time with a timeline that shows trends in your data over time. Through this timeline, you can see how you have improved since the previous version of yourself, and benchmark your progress in comparison. You can view trends over longer periods of time, helping you to make better decisions about where your team needs to go next.

#9 Identifying Reverts and Calculating Pull Request Revert Rate

Oobeya's Pull Request Analytics module now can identify pull request reverts and calculate the pull request revert rate at the team level.

This feature is designed to help teams track their development processes more efficiently and accurately. The new feature allows users to track their pull request revert rate, which is a key indicator of the effectiveness of their development process. This helps teams identify areas that need to be improved.

We’re thrilled to offer this new feature to our users and hope it helps them further refine their processes.

#10 Individual Scorecards Feature on/off Toggle

Oobeya Scorecards allow organizations to gather and track engineering metrics and activities in different dimensions and levels. The Individual Scorecard allows team members to see where they need improvement and identify pending tasks and open issues that require action.

On the other hand, we know some organizations do not prefer to make metrics and activities visible at the individual level. Administrators can enable or disable Individual Scorecards for their organizations by using this toggle. By accessing the Oobeya admin panel, admins now have the ability to toggle the individual scorecards feature on and off, giving them the flexibility to customize their experience with the platform.

  • [Gitwiser] Started to show the list of the running/pending/cloning analyses.

  • [TeamScorecard] Added a technology/language filter for code quality (Sonarqube, SonarCloud) widgets.

  • [TeamScorecard] Added multiple data source selection functionality for Sonar addon.

  • [Admin] Added a "Test Connection" button to the LDAP configuration page.

  • Performance improvements (Pull request analysis, DORA analysis, Symptom detection, and more...)

  • UI/UX improvements (navigating to external tools, design enhancements, new descriptions and tooltips, and more...)

Do you want to see all the new features in action and talk about the product roadmap?

is a cloud-based identity and access management platform that offers secure single sign-on (SSO) and automated user provisioning. By integrating Oobeya with OKTA, users can now access the system securely and quickly.

The integration with OKTA also provides support for SAML-based authentication. is a popular protocol for web-based SSO that provides a secure way for users to securely access multiple applications with a single set of credentials.

We are excited to announce the integration of with , a leading application security platform. As a software engineering intelligence platform, we aim to increase the number of our integrations to give our customers more visibility into their software development and delivery cycles.

Read more on Oobeya Blog:

We’re excited to announce the release of our newest feature for Oobeya: tracking New Relic incidents to detect production failures automatically for calculation. With our new feature, customers can quickly and easily track production failures and calculate their Change Failure Rate without any effort.

Read more on Oobeya Blog:

IMPROVEMENTS

SEE OOBEYA IN ACTION!

Click and now.

💪
🏃
OKTA
SAML (Security Assertion Markup Language)
Oobeya
Veracode
💡
Optimizing Team Performance in Software Development with Oobeya Team Health Module
DORA Metrics
💡
DORA Metrics Tracking: How to Effectively Detect Production Failures
book a demo
🎉
Oobeya Symptoms
Oobeya Team Health [BETA] - Autodetected Symptoms
Bulk User Import From LDAP
LDAP User Sync Button
Oobeya OKTA Integration
Oobeya Veracode Integration
DORA - Tracking New Relic Incidents
DORA - Identifying Hotfix Naming Patterns
DORA Metrics Trends In A Timeline View
Identifying Reverts and Calculating Pull Request Revert Rate
Individual Scorecards Feature on/off Toggle
Recurring high rework rate
Recurring high cognitive load
High weekend activity
High technical debt on Sonar
High vulnerabilities on Sonar
High code quality bugs on Sonar
Unreviewed Pull Requests
Lightning Pull Requests
Oversize Pull Requests
⭐
🎁
Oobeya Symptoms
Oobeya Veracode Integration
Hotfix Pattern Detection
DORA Metrics Trends
Page cover image