* Issue visibility You can currently see an overview of issues and MRs assigned to you (as well as your GitLab TODOs). * Repo access You can narrow repo acce

* Issue visibility You can currently see an overview of issues and MRs assigned to you (as well as your GitLab TODOs). * Repo access You can narrow repo access to a certain group (i.e. make it internal) see [1] * Group-level issue boards We have an open issue for cross-project (group-level) issue boards, see [2] * Multiple repos per project We discussed opting for a non-repo-centric approach to projects in [3] Check out the discussion in there, to see our reasoning for sticking with one repo per project. * Non code projects You can disable the repository in a project, so you can focus on just the issues, or you can have a repository with only graphics. We use both internally. Our organization project doesn't have a repository [4], and our marketing repo has lots of design stuff [5] [1] - https://docs.gitlab.com/ee/user/permissions.html https://docs.gitlab.com/ee/user/permissions.html [2] - https://gitlab.com/gitlab-org/gitlab-ee/issues/928 https://gitlab.com/gitlab-org/gitlab-ee/issues/928 [3] - https://gitlab.com/gitlab-org/gitlab-ee/issues/1295 https://gitlab.com/gitlab-org/gitlab-ee/issues/1295 [4] - https://gitlab.com/gitlab-com/organization/issues https://gitlab.com/gitlab-com/organization/issues [5] - https://gitlab.com/gitlab-com/marketing/tree/master/design https://gitlab.com/gitlab-com/marketing/tree/master/design