Support for multiple "Locations" in bugzilla

Chris L. Mason cmason at
Fri Feb 28 20:44:14 UTC 2003

On Fri, Feb 28, 2003 at 12:21:06PM -0800, J. Paul Reed wrote:
> On 28 Feb 2003 at 11:08:33, Chris L. Mason moved bits on my disk to say:
> > The first thing I'll be working on is support for multiple "locations".
> > We've added the ability to set a Location for each bug.  This was done so
> > that people in one office can just check for bugs related to their office.
> Isn't this just a special case of custom fields?
> Read all about *that* can of worms in bug 91037.

Interesting.  Why not go further and take out the hard-coding of *all*
fields and define them all in a central config file or library with all
the necessary attributes required to support the current functionality.

Anyway, I notice that this patch has been around for awhile and still
hasn't been intregrated into CVS, so I wouldn't want to wait for it.  My
goal is to get this functionality accepted into the official bugzilla
release, in order to keep our custom patches to a mininum (and reduce the
effort involved in migrating to new versions.)  I'd appreciate any 
suggestions you might have for me to help make this more likely.  :)

I'm currently implementing locations similarly to target_milestones so
that the locations can vary by product and can be edited on the product

Btw, another customization we have is the addition of a "system"
milestone.  This is because the "thing" we make has many sub-packages that
each have their own numbering scheme.  So that numbering scheme is handled
with the versions and target milestones, and the "system" milestone is
used for the "distribution" release we ship.

This is similar in concept to the version of a Linux distro such as Debian
3.0 or RedHat 8.0 that contains many packages, each with it's own
independant version number.

Is there perhaps a better way to handle this?  Can anyone else see a use
for this?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <>

More information about the developers mailing list