### Overview As described in https://gitlab.com/gitlab-org/gitlab/-/issues/296972, the concept of segments that was introduced in 13.7 in the DevOps Adoption adds an additional layer of complexity on top of the concepts of groups and projects. ### Proposal For now, we will focus on adding groups and sub groups to the table and remove the concept of segments. If we find over time that we are unable to address use cases with the groups focus, we can revisit and explore options. ### Next steps - [x] [Consider the adoption report a beta feature](https://gitlab.com/gitlab-org/gitlab/-/issues/297434). This gives us flexibility to change the implementation and design so that we're confident we have a good solution in place. - [x] In 13.8, [rename segment to group](https://gitlab.com/gitlab-org/gitlab/-/issues/297445), [backport to 13.7 if possible](https://gitlab.com/gitlab-org/gitlab/-/issues/297445#note_484082789), and limit the number of groups that can be selected to one group. - [x] In 13.8, [Feature flag the Adoption report and disable it by default](https://gitlab.com/gitlab-org/gitlab/-/issues/297434) - [x] In 13.8, [Enable adoption report by default if segments already exist](https://gitlab.com/gitlab-org/gitlab/-/issues/297458) - [x] In 13.8, [limit the adoption report to top-level groups while we investigate the performance impact of including sub groups](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/51565). - [x] In 13.9, [migrate existing segments to the group structure](https://gitlab.com/gitlab-org/gitlab/-/issues/297583). - [x] [Refactor the instance-level modal](https://gitlab.com/gitlab-org/gitlab/-/issues/297641) - [x] In 13.9, [Remove the name input (formerly segment name) in favor of using the group's name](https://gitlab.com/gitlab-org/gitlab/-/issues/297641). - [x] In 13.9, [Restore the ability to select sub-groups](https://gitlab.com/gitlab-org/gitlab/-/issues/299978) (disabled in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/51565). - [x] In 13.10, [Restore ability to select *multiple* records](https://gitlab.com/gitlab-org/gitlab/-/issues/299977) (disabled in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/51574). - [x] In 13.10, [Implement lazy enabling at the instance level](https://gitlab.com/gitlab-org/gitlab/-/issues/299605) - selecting any non-enabled group in the modal will cause it to be enabled automatically. - [x] In 14.0, remove Segments from the GraphQL API - [x] In 14.0, [Change the instance-level feature flag](https://gitlab.com/gitlab-org/gitlab/-/issues/299606) to be enabled by default - [x] Once we've complete the above steps, we should announce the work Martin did to sort columns. That was a customer request and a really nice addition to get a quick view of groups that have/haven't adopted a specific feature.