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
  • 1. What is Account Merging?
  • Why is Account Merging Important?
  • 2. How to Merge Accounts
  • Step-by-Step Guide
  • 3. Best Practices for Merging Accounts
  • When to Merge Accounts
  • When NOT to Merge Accounts

Was this helpful?

  1. DEVELOPMENT ANALYTICS - GITWISER

Merging Contributor Accounts

Learn how to merge duplicate accounts on Oobeya.

PreviousDeployment Analytics (DORA Metrics)NextDORA Metrics Introduction

Last updated 5 months ago

Was this helpful?

1. What is Account Merging?

In collaborative environments, it’s common for contributors to have multiple accounts—whether due to platform integrations, different email addresses, or legacy systems. Oobeya’s Account Merging feature helps streamline contributor data by combining duplicate accounts into a single profile.

Why is Account Merging Important?

  • Accurate Analytics: Prevents duplicate accounts from skewing contribution statistics.

  • Cleaner Data: Maintains a well-organized contributor list.

  • Simplified Management: Easier to track and manage contributions from a single profile.

This feature ensures your team has reliable insights and a clear view of contributor performance.

2. How to Merge Accounts

Oobeya makes it simple to merge duplicate contributor accounts. Follow the steps below to combine accounts efficiently:

Step-by-Step Guide

There are two ways two merge accounts on Oobeya:

Option a):

  1. Navigate to the Gitwiser & DORA Metrics page:

  1. Choose one of the analyses.

  2. Scroll down to the Contributor Statistics table:

  1. Oobeya automatically puts a green indicator next to the name of the contributors who are not connected to an account. Click the indicator, choose which profile you want to merge this contributor with, and click Merge:

  1. The accounts will be combined, and the contributor's data will now be consolidated under the selected profile.

Option b):

  1. Navigate to the Team Health page.

  1. Click on Profiles, click on the Manage Profile icon and Update Profile on the profile you want to merge accounts with:

  1. On this page, you can see the accounts that have been merged with this profile, unmerge them, and also merge new accounts by clicking on the Add Account button.

3. Best Practices for Merging Accounts

To ensure smooth and effective account management, follow these best practices when merging contributor accounts:

When to Merge Accounts

  • Duplicate Profiles: Merge accounts that represent the same contributor but appear under different usernames or email addresses.

  • Inactive Accounts: If a contributor has an outdated account alongside an active one, merge them to avoid confusion.

  • Platform Integrations: Accounts created through integrations (e.g., GitLab, GitHub) might sometimes duplicate; merge them to maintain consistency.

When NOT to Merge Accounts

  • Different Contributors: Avoid merging accounts if they belong to different individuals, even if they have similar names or emails.

  • Unverified Accounts: If you're unsure whether two accounts represent the same person, verify before merging.

Oobeya's Account Merging feature simplifies contributor management by consolidating duplicate profiles into a single, accurate account. This ensures cleaner data, more reliable analytics, and easier contributor tracking.

By following the steps outlined in this guide and adhering to the best practices, you can maintain a well-organized contributor list and avoid data inconsistencies.