Akhil Srinivasan
> Hi
> We just managed to setup Bugzilla on my Redhat 7.3 Server. Since we will be
> working on multiple projects. I had hoped to just install another instance
> of bugzilla and create a new database for every other project.
> Will this work? and Is there any config issues that I should be carefull
> with?
Works just fine. Look at http://landfill.bugzilla.org/ for an example.
There's probably about 50 copies of Bugzilla running on that box (no I'm
not kidding).
However, "multiple projects" doesn't sound like a real good reason when
taken at face value. Why not just set up a different product for each
project in Bugzilla? (or is there more to it than that?)
--
Dave Miller Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/ http://www.bugzilla.org/
Akhil Srinivasan
"Dave Miller" <bugd...@syndicomm.com> wrote in message
news:a05210505babb78dc350a@[192.168.1.203]...
By product I mean the things you set up in "editproducts.cgi". There
should be a link in the footer when you're logged in as the admin (probably
says "components" in the version you have, it says "products" in the newer
versions) that goes there.
You'll regret that the first time someone wants to move bugs from one
project to another, or reorganise the projects, or search across
multiple projects, or upgrade to a later version of Bugzilla, or make
some customisations.
Use a single Bugzilla, with Bugzilla "Products" for your projects, and
"Components" for your parts of projects. Believe me, it's far less hassle.
Gerv
Akhil Srinivasan
"Gervase Markham" <ge...@mozilla.org> wrote in message
news:b763et$an...@ripley.netscape.com...
Akhil Srinivasan wrote:
> Thanks, but first I need to keep users of one project from accessing the
> bugs in another project. I saw the groups page in bugzill admin, but im not
> sure how it works? and how secure it is?
It's pretty secure :-) It works very differently in 2.16 and 2.17, so
you'd have to say which version you were running.
> If possible I need to make sure that users not know that multiple projects
> exist.
That should be possible. You may have to disable some of the reporting
functions, which currently leak this information.
Gerv
I do exactly this on a site where my own employees work with multiple
customers who can not see each other's projects at all. Buglists are
secure, but all the reporting (charting) functions are restricted to a
group of users who are allowed to see all the projects.
-Joel
"Joel Peshkin" <bugr...@peshkin.net> wrote in message
news:b7fhqv$qr...@ripley.netscape.com...
If you switched them on after you created the products, then you need to
create groups with the same name as the products (this is what happens
when you create products with usebuggroups switched on.) Then, the right
thing will happen.
Gerv
Akhil Srinivasan
"Gervase Markham" <ge...@mozilla.org> wrote in message
news:b7h65v$gu...@ripley.netscape.com...