[rcthompson]

I think the real angle of this feature should be to abstract the concept of "project" so that it is no longer synonymous with "git repository". And the migration path is pretty straightforward: every repo becomes a project containing a single repo, and then users can merge existing projects to create multi-repo projects (at which point you'd probably have to re-number every issue, pull request, etc. to avoid collisions).

[chetanahuja]

We use gitlab at PacketZoom too and are mostly happy with this. But yes, I second the request for either:

a) Creation of a project independent of git repos.

OR

b) At least a way to attach issues across projects. Issue management is probably the weakest part of gitlab and one of the big reasons is this fragmentation of issues across git repos. It's trivial to see that issues can and will cut across git repos in any reasonably complex product. Another "nice to have" feature would be an ability to create "dependent" issues.

[sytse]

We looked into this but it creates a lot of complexity. The group milestone view solve the problem neatly.

[rcthompson]

That seems pretty reasonable, maybe even preferable. Having issues attached to specific repos but synchronized to cross-repo common milestones sounds like it would work well.

[sytse]

Thanks! To give you an idea of how it looks I've attached a screenshot of our group milestone overview https://www.dropbox.com/s/ectdan1qc22vd3k/Screenshot%202015-... and a specific milestone https://www.dropbox.com/s/rqb6rhaxafrmrtn/Screenshot%202015-...

[BinaryIdiot]

I like this way of organizing. At my last company we had a very, vary large project that had about 70 git repos (and that was after combining quite a few of them). A project view would have made that so much easier to manage.