Solution with multiple projects and (GitHub) single issue tracker and repository
        Posted  
        
            by 
                Luiz Damim
            
        on Programmers
        
        See other posts from Programmers
        
            or by Luiz Damim
        
        
        
        Published on 2013-05-02T11:24:45Z
        Indexed on 
            2013/10/31
            10:19 UTC
        
        
        Read the original article
        Hit count: 423
        
I have a Visual Studio solution with multiple projects:
Acme.CoreAcme.Core.TestsAcme.UI.MvcSite1Acme.UI.MvcSite2Acme.UI.WinformsApp1Acme.UI.WinformsApp2- ...
 
The entire solution is checked-in in a single GitHub (private) repo. Acme.Core contains our business logic and all UI projects are deployables. UI projects have different requirements and features, but some of them are implemented in more than one project.
All issues are opened in a single issue tracker and classified using labels ([MvcSite1], [WinformsApp1], etc) but I'm thinking it's starting to get messy.
Is it ok to use a single repository and issue tracker to track multiple projects in one solution?
© Programmers or respective owner