Feature: 1 project = n repositories
Created by: kelas
(discussion started in #1289 (closed))
In an enterprise setting, a project is hardly ever represented by a single repository. Big shops have many teams, teams have multiple projects, and projects have multiple repositories.
A flat list of GitLab repositories grows unmanageable very quickly, imposing obscure naming conventions, making issue tracking difficult, granting/revoking permissions becomes a mess, etc etc
Would be great if future version of Gitlab supported one-to-many relationships between Projects and Repos as seen in Atlassian Stash.
It should be possible to attach issues to whole projects, not only specific repos - it is then up to assigned developer to identify a target repo to apply a fix.
Thoughts, anyone?