bug was actually a legal bug number.

should have always had this behavior.

different fields we keep an activity log on.  The bugs_activity table
now has a pointer into that table instead of recording the name directly.

Set up a new, highly experimental email-notification scheme.  To turn
it on, the maintainer has to turn on the "New email tech" param, and
then individual users have to turn on the "New email tech" preference.

table.  There is now a separate entry for each new long description,
rather than appending them all together in one big field.

of all the keywords assigned to the bug.  Right now, we only have code
that generates and maintains this field; soon will come code that
actually uses it.

reassigning by component, reassign the qa contact too.

me.  Added a footer to every page.  Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.

away from them or they get removed from the CC list.

changing keywords.

field.  This caused mid-air collisions and other weirdnesses.

authority maintain a list of keywords, and users can associate any
keyword with any bug.

The new functionality won't appear until at least one keyword is
defined.

Note that you *must* run the "checksetup.pl" script after updating
this change, in order to create the new required tables "keywords" and
"keyworddefs".

Patch by freitag@suse.de (Klaas Freitag) -- add options to let Bugzilla require comments on certain operations.

reassign-to-component-owner.

be fixed.

Patch by holger@holger.om.org (Holger Schurig) -- put the fancy header on several pages that were missing it.

use "when" as a column name, so let's change our usage while it's
still easy to do so.

other ones.

py8ieh=bugzilla@bath.ac.uk).

the change (after all, they are right there viewing things interactively).
To make this clear to everyone, print out the exact email list as each
bug is processed.

put on a person or on a bug.  Some of the group bits control access to bugzilla
features.  And a person can't access a bug unless he has every group bit set
that is also set on the bug.

turned on): target_milestone, qa_contact, and status_whiteboard.

an invalid component or version field.  (Like, for example, all the
new NGLayout bugs.)