Default project (issues) for group level free-flow discussion and collaboration
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Teams and products and applications often organize themselves in groups, not projects. In a typical organization, that heavily uses (micro)services, each team that is responsible for a particular product, maybe organized in a group. The projects in that group may just simply be wrappers of code repositories. So the team would use the projects for merge requests to make code changes.
However, the actual project management and tracking of ideas and doing Agile/Scrum/Kanban should be done at the group level. Because team-level work is done at the group. Actual code implementation is at the project-level.
So therefore, when the team wants to start an idea or have a free-flow discussion, we should not force them to pick a project, and create an issue. They should be able to easily start at the group, and start a discussion.
Having a "group issue" could solve this. But in our current GitLab design, we have reserved the group-level native work abstraction to be an epic. So we could ask teams to use epics. But epics are more "heavy", in that they represent higher level concepts and business initiatives. Furthermore, they don't have the flexibility and power of free-flowing issues.
So the proposal here is to have a default project associated with groups. And so teams would be able to create issues starting at the group level, but they wouldn't be forced to pick a project, because GitLab has already defaulted a project for you.
It's not clear from a design perspective how this would work yet. Would we expose the project to the user? Would we allow the the team to specify/change the default project?
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.