Post-Reorganization Cleanup and Ownership Mapping

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue

Problem Statement

Following the dissolution of the Import and Integrate team and subsequent organizational changes, there are multiple systemic issues affecting code review, support escalation, and feature ownership across GitLab:

Immediate Issues Identified

1. Broken Code Review Process: Reviewer Roulette still points to non-existent team channels (import_integrate_be, import_integrate_fe)
2. Documentation Gaps: Integration docs pages show no "stage" or "group" assignments
3. Support Escalation Confusion: Support tickets get shuffled between teams (example: issue moved from authorization → authentication → subscription management → seat management)
4. Domain Expertise Loss: Features lack clear domain expert review, leading to regressions

Systemic Problems

• Feature category mapping system not kept up to date after reorganizations
• "Shared" or "not owned" categories leading to responsibility gaps
• No clear escalation path when ownership is unclear
• Gradual drift of subject matter expertise as people move away from features

Scope

Phase 1: Immediate Cleanup (This Issue)

• Remove obsolete team references from Reviewer Roulette configuration
• Audit and update integration documentation with correct stage/group assignments
• Identify other areas with broken team references from Import & Integrate dissolution

Phase 2: Systematic Ownership Review (Follow-up Issues)

• Audit feature category mappings for accuracy post-reorganization
• Review and update bounded contexts ownership

Acceptance Criteria

Immediate Fixes

• import_integrate_be and import_integrate_fe references removed from Danger roulette configuration
• Integration documentation updated with current stage/group assignments
• No broken team references in reviewer assignment systems

Process Improvements

• Document escalation path for unclear ownership situations
• Create checklist for PM teams to update feature mappings during reorganizations
• Establish regular audit process for team mapping accuracy

Related Work

• Original issue: #549006 (closed)
• Danger roulette introduction: !74330 (merged)
• Support toolbox for finding right person: https://gitlab-com.gitlab.io/support/toolbox/engineering-directory/
• Feature category mapping: https://handbook.gitlab.com/handbook/product/categories/
• Bounded contexts documentation: https://docs.gitlab.com/development/software_design/#bounded-contexts

Implementation Notes

Technical Changes Needed

1. Reviewer Roulette Configuration

   • Remove import_integrate_be and import_integrate_fe from danger configuration
   • Map affected areas to current responsible teams

2. Documentation Updates

   • Audit integration pages for missing stage/group assignments
   • Update with current team ownership

3. Feature Category Mapping

   • Review config/bounded_contexts.yml for orphaned contexts
   • Ensure all contexts have active team ownership

Process Changes

1. Reorganization Checklist

   • PM responsibility to update feature mappings
   • Engineering responsibility to update code review assignments
   • Documentation team responsibility to update handbook pages

2. Regular Maintenance

   • Quarterly audit of team mappings
   • Integration with reorganization planning process

Success Metrics

• Zero broken team references in code review systems
• Reduced support ticket shuffling between teams
• Faster resolution of ownership questions
• Maintained domain expertise in code reviews

Labels

• type::maintenance
• workflow::ready for development
• documentation