Reworked preferences UI. Added ability to turn off "My bugs" link at
bottom. Made "My bugs" show bugs you own AND bugs you submitted.
Added ability to display your named queries in the footer. Many
random bugfixes.
Named queries (and the default query) are now stored server side, in
the database, rather than in cookies. This means you have to log
in to use these features, but I have plans that require them to be
server-side. (Besides, some people were beginning to run out of
cookie space.)
The "login_name" field in the "profiles" table was not declared to be
unique. Sure enough, somehow, I got 22 duplicated entries in my
database. This code detects that, cleans up the duplicates, and then
tweaks the table to declare the field to be unique. What a pain.
AACK! checksetup.pl was stomping all over the new fielddefs table if
it got run more than once. This checkin fixes that, and also changes
the DumpBugActivity() routine to give me enough information to
hopefully repair the damaged mozilla.org database...
Remember the previous sort order in a cookie, and make that the
default sort order for new queries. Add a new "show list" link to the
navigation header to return you to the list of selected bugs.
Patch by Christine Begle <cbegle@mozilla.org>>, with heavy
modifications by me -- let you query for "any words" and "all words",
as well as the existing substring and regexp stuff.
Patch by Klaas Freitag <freitag@suse.de>, with modifications by me --
don't generate HTML tables with more than 50 lines, as browsers generally
can't cope with huge tables.
Patch by Holger Schurig <holger@holger.om.org> -- add new localconfig
option to skip the database check (since that code doesn't work with
all versions of MySQL/Msql-mysql/Perl/moonphase).
Added a new table fielddefs that records information about the
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.
Moved all the long descriptions out of the bugs table, and into a new
table. There is now a separate entry for each new long description,
rather than appending them all together in one big field.
Use new "keywords" cache to display keywords in bug lists. Not only
is this much faster, but it also lets you sort by that column, and
requires less special-case code.
Added a "keywords" field to a bug, which is a cached string-based copy
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.
Patch by Ramon Felciano <felciano@ingenuity.com>, with many tweaks by
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.
Add support for a new "keywords" feature. This lets some central
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".
A few months ago, we lost the ability to edit the votes-per-user field
in a product. Which meant nobody could turn on or off this feature.
Restored the editing ability.
Fixed very very nasty bug which, when deleting a component, would tell
you it had no bugs (even when it had some), and would then proceed to
delete all those bugs (even if you had the param set to never allow
bug deletion.) Added some paranoia to prevent such things from
happening again. Yikes.
Whoops! Was reporting ASSIGNED bugs as being closed. Also, changed
it to report the resolution of the bug instead of the word "closed".
Many thanks to dbaron@fas.harvard.edu for suggesting this change, and
reporting the bug.
Due to popular request, "bug changed" mail will only report changes in
state on dependent bugs if they move from an 'open' to a 'closed'
state, or visa-versa. Also, if there are more than 5 bugs on the
list, then we won't even try to generate the details (doing so only
generates lots of extra mail that is too hard to parse anyway.)