The project strucutre seems completely the wrong way round. Projects live independently of repos, but a project usually has more than one repo. E.g. a project to build a new e-commerce platform will have a "core" repo, a "backofice" repo, a "web" repo, etc. There may be 10 or more, but usualy 2-6 in our cases. Github, for some unknown reason, has the relatioship back to front. A repo doesnt have a project - a project has a repo! I see that github has added "linking" up to 5 repos to a project. But this seems like an ineffective attempt to fix it: the repo doesnt know its in the project (projects are listed as zero), when you are looking at the kanban for the project, it lists all your (400+) repos on the left, not just the linked ones. When you create a new board item in your project, then convert to issue (we ALWAYS convert to issue, this 2 step proccess is a pain), it asks for repo, and you have to manually search all (400) of your repos. It should have a drop down of your linked repos, but doesnt. etc. etc. So to sumarise: I belive that the project/repo relationship is wrong, and should be reversed. it should allow any number of repositories to belong to a project, not just 5. When adding an issue to a project, it should only show you repos of that project. When viewing the board of a project,it should only show the list of that projects repos on the left. In theory, a repo could belong in multiple projects, but we could live without this if its too hard for github to implement this.
... View more