id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 2262 manage multiple projects better. anonymous Jonas Borgström "it would be really helpful if trac had a better way to manage multiple projects. I know right now you can have multiple trac instances running against a single subversion repository which is somewhat helpful as long as the projects are set up to be independent. However, if a developer is working on many projects, multiple trac locations need to be browsed (or RSS etc) in order to stay on top of what's going on. Likewise if one project is a dependency for another project it's difficult to manage where issues get created and tracked. Having one big trac instance doesn't help because you can only specify a component when entering a ticket not a product. I think trac is a great product but it starts to break down when used in a enterprise environement. I think all this requires is a slight tweak in the work flow. With custom reports its fairly easy to manage multiple projects within trac if you were able to select a product when entering a ticket. " enhancement closed high general 0.8.4 normal duplicate