Description of problem:
Problem:

There is no easy way to track regression introduced by a particular BZ right now from the Bugzilla. As the results, our metrics are unable to provide something like outsourced partners tested BZs' introduced regression rate and a particular QA contact person/team's tested BZs' introduced regression rate. Those metrics would be useful to measure the efficiency of our testing efforts. For example, by combined of those information in BZ, we can find out how many partners tested BZs that introduced regression but found out later by customers (bad) and found out and resolved in the same release by partners themselves (good).


Proposal:

Add an additional field in Bugzilla.
- Introduced regression: to list a regression BZs that the code change for this particular BZ introduced.

If there a BZ has the "Keywords" Regression, there will be an optional field called regression source to specify the BZ number which is the source that introduced this regression if known. This is also to save an additional field space in BZ to be able to do 2-way mapping - from a regression BZ to find out its source and from the regression source to a list of regression BZs introduced.

For example,

BZ#foo was found to be a regression introduced by BZ#bar.

On one hand, we can add a regression keyword to BZ#foo and then an optional field - regression source to be filled with the regression source BZ#bar. Automatically, BZ#bar's "Introduced regression" field will be updated to include the BZ#foo.

On the other hand, we can add BZ#foo to the "Introduced regression" field of BZ#bar. Then, BZ#foo will be added a regression keyword if not, and have the associated regression source field set to BZ#bar.