How many database we should have for Bugzilla? - Mozilla

This is a discussion on How many database we should have for Bugzilla? - Mozilla ; In our company, we have about 5 lines of business planning to share one centralized Bugzilla installation. Under each line of business, we would have many products. I need your help to have some suggestions on how many database we ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: How many database we should have for Bugzilla?

  1. How many database we should have for Bugzilla?

    In our company, we have about 5 lines of business planning to share one
    centralized Bugzilla installation. Under each line of business, we would
    have many products. I need your help to have some suggestions on how many
    database we should set up.

    As a designer, who used to set up Bugzilla for his team, suggested to have
    separate database for different line of business. As we understand, we are
    only allowed to have separate settings based on database, and products on
    the same database have to share the same settings.

    I need your help to have some suggestions on how many database we need set
    up, in terms of various line of business (or various product) require
    different settings.

    Thanks advanced!

    Jessie



  2. RE: How many database we should have for Bugzilla?

    Quoting Jessie Li:
    > In our company, we have about 5 lines of business planning to share
    > one centralized Bugzilla installation. Under each line of business,
    > we would have many products. I need your help to have some
    > suggestions on how many database we should set up.
    >
    > As a designer, who used to set up Bugzilla for his team, suggested to
    > have separate database for different line of business. As we
    > understand, we are only allowed to have separate settings based on
    > database, and products on
    > the same database have to share the same settings.
    >
    > I need your help to have some suggestions on how many database we
    > need set up, in terms of various line of business (or various
    > product) require different settings.


    That sounds like a very specific question that only you could answer.
    My suggestion is to start with all products in the same database, but
    document a migration plan to move groups out to separate databases as
    needs arise.

    I would suggest that you get a list of all products and try to group by
    similar functional needs. Or you can group by LOB.

    I have set up multiple databases using Aliases and Location directives,
    so it isn't that difficult. I've just never had to 'move' bugs from one
    database to another, but I understand it isn't that difficult.



    ## Group 1, that has been using bugzilla for a while
    Alias /group1 /var/www/htdocs/bugzilla

    SetEnv PROJECT group1


    SetEnv PROJECT group1


    ## Group 2 is new to bugzilla
    Alias /group2 /var/www/htdocs/bugzilla

    SetEnv PROJECT group2


    ## Base Bugzilla directives

    AddHandler cgi-script .cgi
    Options +Indexes +ExecCGI
    DirectoryIndex index.cgi
    AllowOverride Limit Indexes


  3. Re: How many database we should have for Bugzilla?

    On Wed, 30 Apr 2008 15:42:51 -0400 "Jessie Li"
    wrote:
    > As a designer, who used to set up Bugzilla for his team, suggested to
    > have separate database for different line of business.


    Most people who set up multiple Bugzillas eventually decide to
    merge them into one Bugzilla, which is a big hassle that could have
    been avoided by just using one Bugzilla to start with.

    -Max
    --
    http://www.everythingsolved.com/
    Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

+ Reply to Thread