FY27 Source Code - Organizations Compatibility
Source Code tracking for delivering on Organizations compatibility by FY27-Q2.
Epic
Parent Issue(s)
- Organizations Feature Parity: Create – Source Code (gitlab-com/gl-infra&1893)
- [s_CREATE]::SOURCE CODE MANAGEMENT (gitlab-org#20702)
Overview
We are introducing a higher level abstraction called "Organizations" as a top-level administrative layer encapsulating groups, project and teams. The engineering goal is to introduce organizations with no impact to existing workflows or features.
Guidelines
- Step by Step Guide for Product Teams
- Source Code Feature Compatibility Assessment
- Organizations Technical Guidance
Associated work will happen in two steps:
- FY27-Q1: Complete self-assessment
- FY27-Q2: Implementation, Validation and Testing
High-Level Roadmap
Step 1: Complete Self-Assessment
-
Under the feature parity epic find your group's self-assessment work item (e.g., The Geo team will find their self-assessment in Tenant Scale > Geo).
- Source Code self-assessment: https://gitlab.com/gitlab-com/gl-infra/tenant-scale/organizations/organizations-feature-parity/-/work_items/11
- Complete the self-assessment questionnaire for your group.
- Ping the Organizations team members for review and closure.
- Any identified gaps need to be addressed in FY27-Q2. Create follow-up issues under your section/group epic.
Note: use the spreadsheet here to track compatibility. Detail any gaps, blockers or dependencies
Step 2: Implementation and Testing
Following results from step-1 we'll update this section with a more detailed timeline for implementation and testing by eligible feature.
- Create development issues for all in-scope features in Source Code
- Add weight estimates to each development issue
- Complete Database Query Scoping
- Complete Permission and Authorization Updates
- Complete API Endpoint Updates
- Complete Background Job Handling
Edited by Andre Richards