[Trac-tickets] Re: [The Trac Project] #130: Multi-project support

[The Trac Project]

#130: Multi-project support
-------------------------+--------------------------------------------------
       Id:  130          |      Status:  reopened                
Component:  general      |    Modified:  Mon Apr  4 09:35:06 2005
 Severity:  enhancement  |   Milestone:  2.0                     
 Priority:  normal       |     Version:  devel                   
    Owner:  jonas        |    Reporter:  anonymous               
-------------------------+--------------------------------------------------
Comment (by garyo):

 Hi, I'm a new potential user of trac.  It looks beautiful, but the lack of
 subprojects is a showstopper for us.

 In our situation, we produce multiple products from the same source
 repository (we write plug-ins and they plug into various host products).
 Each product/subproject has its own version numbering, components, and
 milestones but our whole world is in a single svn repo.  So for us the
 repository ambiguity referred to above would not be an issue.  We would be
 happy just to have a 'project' table and have the other tables refer to
 it, and have the reports adjusted appropriately.

 Multiple separate tracs are not good for us, since tickets may refer to
 the whole system (not just a single project), and we'd like to be able to
 move a ticket from one subproject to another easily (e.g. by just changing
 its project id), and we '''definitely''' need a merged timeline and
 roadmap (what's coming up soon?)

 This limited change seems pretty simple.  Would enough people be
 interested in it to make it worthwhile?

 -- Gary O

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/130>
The Trac Project <>