This epic collects efforts to move features to the namespace framework with the goal in mind to make them available at both the group and project level, when earlier they were only available at either the group or project level. # Features owned by ~"group::organization" - [ ] ~"group::organization" [MVC - Create an option to archive/unarchive groups](https://gitlab.com/gitlab-org/gitlab/-/issues/15967) - [ ] ~"group::organization" [MVC - Allow to star groups (and subgroups)](https://gitlab.com/gitlab-org/gitlab/-/issues/23576) # Features owned by other teams ## Dev ### Plan - [ ] ~"group::optimize" [Make Value Stream Analytics available at the project level](https://gitlab.com/groups/gitlab-org/-/epics/6796) - [ ] ~"group::project management" https://gitlab.com/groups/gitlab-org/-/epics/8308+ - [ ] ~"group::project management" https://gitlab.com/gitlab-org/gitlab/-/issues/338820+ - [ ] ~"group::project management" Milestones - [ ] ~"group::project management" Iterations - [ ] ~"group::project management" Planning settings - [ ] ~"group::product planning" https://gitlab.com/groups/gitlab-org/-/epics/8308+ ### Manage - [ ] ~"group::authentication and authorization" Synchronize `lfs_enabled` setting: This is currently on both group and project level, with two columns in both tables. Con: not user-facing. ### Create - [ ] ~"group::source code" Move make committer email be configurable for groups or projects to namespaces - [ ] ~"group::editor" Migrate project and group wikis to namespace ## Ops ### Verify - [ ] ~"group::pipeline execution" Merge Trains - [ ] ~"group::pipeline execution" Pipeline Must Succeed - [ ] ~"group::pipeline execution" https://gitlab.com/gitlab-org/gitlab/-/issues/342842+ - [ ] ~"group::pipeline execution" https://gitlab.com/gitlab-org/gitlab/-/issues/21725+ - [ ] ~"group::pipeline insights" https://gitlab.com/gitlab-org/gitlab/-/issues/299304+ - [ ] ~"group::runner" https://gitlab.com/gitlab-org/gitlab/-/issues/349071+ ### Package - [ ] ~"group::container registry" https://gitlab.com/gitlab-org/gitlab/-/issues/323773+ ### Release ### Configure ### Monitor ## Sec ### Secure - [x] ~"group::security policies" [Security policy management](https://docs.gitlab.com/ee/user/application_security/policies/?_gl=1*19besak*_ga*MTM2MDEzNjY0OS4xNjY1MzgxOTg1*_ga_ENFH3X7M5Y*MTY2ODYxNDMwMC4yMjUuMS4xNjY4NjE0MzE3LjAuMC4w) ### Govern - [ ] ~"group::compliance" Consolidate Push Rules: They exist on instance, groups, and projects - reduce tech debt ## Data Science ### ModelOps - [ ] ~"group::applied ml" We need to find a way to bring automation from the project level to the group level. # TBD * Group-level service integrations https://gitlab.com/groups/gitlab-org/-/epics/2137 * Group-level Mattermost and Slack command integrations * Group-level subscriptions * Group-level container registry view * Deploy a group of services at once * Pipelines that span a group? * Group merge requests: https://gitlab.com/groups/gitlab-org/-/epics/457 * https://gitlab.com/gitlab-org/gitlab/-/issues/8140+ * Add CI/CD Analytics to group or instance - Overall statistics to group: These are just numeric statistics and currently only exist on Project