In multi-tool environments, a single developer often appears under multiple identities across systems (for example, different email IDs or username variations in Jira, GitHub, SCMs, or CI tools). Today, SEI primarily relies on a single canonical identity (often sourced from the Developer CSV or a primary system). This results in fragmented attribution, partial metrics, and inaccurate developer- and team-level insights when additional identities are not automatically reconciled.

Example Scenario

A developer is configured in SEI with abc@PQR.com, but appears as ab@xyz.com in GitHub and ab@gmail.com in Jira. As a result, work is split across multiple “developers,” leading to incomplete productivity, flow, and delivery metrics.

Proposed Change

Introduce heuristic-based auto identity discovery during ingestion and processing, to automatically map multiple identities to a single logical developer in SEI.

Key Capabilities

Heuristic-Based Identity Matching

Apply configurable heuristics during ingestion, such as:

Name similarity (exact, fuzzy, normalized)

Username patterns

Email local-part similarity

Historical co-occurrence across systems (PR author, commit author, Jira assignee/reporter)

Assign a confidence score to each inferred identity match.

Confidence-Driven Auto-Merge

High-confidence matches are automatically merged into a single developer identity.

The canonical developer remains the one defined via Developer CSV (or primary identity source), with additional identities linked as aliases.

Admin / Team Manager Review for Low Confidence Matches

When confidence falls below a defined threshold:

Surface a list of potential identity matches in the UI.

Allow SEI Admins or Team Managers to manually confirm, reject, or adjust mappings.

Decisions are persisted and reused for future ingestions.

Auditability and Control

Maintain an audit trail of:

Auto-merged identities

Manually approved or rejected mappings

Provide the ability to unmerge or reassign identities if needed.