Matthew Tuck [:CodeMachine] Reporter
	Description • 23 years ago

We need a bug integrity framework.  It should check that the values of bugs'
fields (including their relationships with other bugs) makes sense.

Certain relationships could be hardcoded into the system, but possibly able to
be turned off.  Eventually, an administrator could define new relationships.

I suggest that we should separate relationships into MUST and SHOULD.

MUST relationships could be implemented by refusing to make changes that would
violate the relationships, or alternatively, updating certain fields in order to
satisfy the relationship.

These would be problematic between (dependent) bugs, because the other bug might
be the one you should be fixing.

SHOULD relationships would present a confirmation page confirming that the
relationship being broken was OK.

The process_bug screen should list all the current problems with that bug,
except for those that have just been confirmed (ie all relationships that were
previously broken but weren't just broken).

Eventually, whinemail should be sent about about all of these problems as well.

	Matthew Tuck [:CodeMachine] Reporter
	Comment 1 • 23 years ago

Moving to new Bugzilla product ...

	Myk Melez [:myk] [@mykmelez]
	Comment 2 • 23 years ago

At least part of this problem can be solved by migrating to a database with
referential integrity (or requiring a version of MySQL that has this feature).

	Matthew Tuck [:CodeMachine] Reporter
	Comment 3 • 23 years ago

I'm not sure whether we should reflect these in the database.  It makes sense I
guess, but something about making the Bugzilla schema partially dynamic doesn't
seem right to me.

	Max Kanat-Alexander
	Comment 4 • 17 years ago

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.

	Frédéric Buclin
	Comment 5 • 14 years ago

I don't know what this bug is trying to achieve, but this is wontfix for me for the following reasons:

- Bugzilla now uses referential integrity into the DB itself

- No hardcoded restrictions should be implemented. Each company has its own rules, and those should be enforced thanks to an extension, if needed.