Skip to content
GitLab Next
Open
Created by Mark Pundsack@markpundsackContributor7 of 15 tasks completed7/15 tasks

Group level things

Most companies do not work in a single project, yet all of our functionality is optimized around the project. We need to recognize that companies have many teams, with many projects, and some projects are composed of many components (e.g. micro-services). While the relationship between these pieces is not always rigidly hierarchical, the addition of sub-groups gives us a chance to step in that direction. Imagine a company, with several departments, each with multiple apps composed of many services. e.g. gitlab.com/company/dept/app/service/issues. Now, the structure can already happen, but what about issues that span all the services in an app? Or issues that affect an entire department or even the whole company? We need to start supporting features at the group (and sub-group) level.

Note, the group mapping will be imperfect. Some teams will share a service in multiple apps, for example. Or an issue might span 2 departments, but not all of them. But let's not let that get in the way of delivering value now. Let's see how far we can push the sub-group orientation.

Edited by Gabe Weaver