Modifying Bugzilla to track a bug across multiple versions with different statuses

Dave Williss dwilliss at
Fri Jan 7 15:10:11 UTC 2005

We have a similar situation.  The solution we came up with is that when a 
bug is
reported, the version is set to the earliest version the bug is known to 
exist in.
When an engineer fixes it, they're supposed to fix all versions from current 
If, for some reason, they can't, they set the target milestone to the 
earliest version
that they fixed.

Another good idea would be to define flags for each version specifying if 
the bug
exists in that version and another one for if it's fixed in that version.

----- Original Message ----- 
From: "Keoni Jacobsen" 
<bugzilla-AT-obmutescentthiophen-DOT-mine-DOT-nu at nospam.invalid>
To: <developers at>
Sent: Friday, January 07, 2005 1:03 AM
Subject: Modifying Bugzilla to track a bug across multiple versions with 
different statuses

>I am the Bugzilla guru for the company I work for.  We want to modify
> Bugzilla, and I was looking for advice on how to do this.  I'm not
> asking for any technical help.  We have good people working on this.
> (Well, it's just me, but I can handle it.)  I was trying to figure out
> how to make this look for the users and managers.
> Here is the situation: we have bugs and we have different versions of
> our product.  We can find bugs in one version of our product, and we
> know it may exist in other versions of our product.  A bug can get
> fixed in one version, but, life being what it is, it may not get fixed
> in other versions.
> We want to be able to track what versions a bug appears in, and where
> it gets fixed.  So, the single bug status isn't adequate for this.  We
> can't just say a bug is resolved if it's fixed in the most recent
> version if it isn't fixed in the previous version.
> What we've been doing is opening up new bugs for each version.  But
> it's a pain trying to keep all the bugs straight, and seeing what bugs
> are really the same as other bugs, just in different versions.  It
> messes up bug dependencies, and it makes it hard to link to our
> customer issues.
> So, I want to find a way to make things easier on everybody.  What
> scheme would you suggest?
> -KJ
> P.S. Please forgive the obfuscated E-mail address.  I'm just trying to
> avoid the plague of the Internet (aka spam).
> -
> To view or change your list settings, click here:
> <> 

More information about the developers mailing list