Hello Roman, > Thank you for the links, it was very interesting reading. Your > experience also seems to caution against similar situations. In my > previous job, we were also using Trac for multiple projects (namely > 4), but they were really a separate projects so I can't say a lot > about MultiProjects settings - but on the other hand, I can easily > imagine it. > > But the basic question IMHO is whether CDS and INSPIRE need to be > separate - whether they are INDEPENDENT - I don't think anyone can > answer "yes" to that question, at least for inspire. Or if they are > SEPARATE - answer might be yes, but separate in which way?
In our case, the gravity point was people rather than projects. *I* want to know which high priority tickets do *I* have, regardless how (un)related the projects are. We want to know how many tickets are open since whatever, regardless the project. You can't do that with multiple Trac instances. > If "not technically", then is there a real need for MultiProjects > setup? By this simple consideration array of technical nightmares > might be gone, and if that is solved, there is no need to solve other > stuff. Especially when 7 days ago Trac rolled out their > MultiRepository support: > http://trac.edgewall.org/ticket/130#comment:145 I didn't know about this new development, but they insist so much that their target is single-instance-single-project, and the #130 ticked is so old, that I fear that it might not be very clean. There is something more about Trac that confused me and my coworkers, and it is shared with Retrospectiva, I think (we haven't evaluated them thoroughly): this confusion between Login (which is unneeded to fill tickets) and Preferences. In our internal working scenario, we thought it was clearer to force a login before adding tickets or edit wiki pages. In both DrProject and Redmine you have to login and then you can set your preferences. I don't know enough about Basie. Ferran
