Feature: Team Hierarchy and Organizational Mapping

[bob-duetto]

Summary

Add support for team hierarchy to enable team-level aggregation and manager rollups.

Background

DX platform tracks 21 teams in hierarchical structure with:

• Parent/child team relationships
• Team membership
• Team-to-repository ownership
• Manager assignments

Requirements

• Add teams module under src/gitflow_analytics/core/
• Support team definition via YAML config
• Map developers to teams
• Map repositories to team ownership
• Support hierarchical aggregation (team → parent team → org)
• Add --by-team grouping option to CLI

Data Model

# teams.yaml
teams:
  - id: engineering
    name: Engineering
    manager: jane.doe@example.com
    children:
      - id: platform
        name: Platform Team
        members:
          - john.smith@example.com
        repositories:
          - repo-a
          - repo-b

Acceptance Criteria

• Report shows metrics aggregated by team
• Manager rollup view (all reports' metrics)
• Team-level DORA metrics comparison
• Export team hierarchy to JSON

Priority

Medium - Enables management reporting

🤖 Generated with Claude Code

[bobmatnyc]

Deferred

Team hierarchy and organizational mapping is useful for management reporting, but the current tooling already supports team-level grouping via developer_aliases/manual_mappings and custom config. A full hierarchical team model with parent/child relationships is out of scope for the near term.

Closing as deferred.