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.)
git-svn-id: svn://10.0.0.236/trunk@58443 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58386 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58008 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@57846 18797224-902f-48f8-a5cc-f745e15eee43
of votes that have been cast for that bug. This let me simplify the
SQL in buglist.cgi, which makes things more efficient and fixes
several strange bugs.
git-svn-id: svn://10.0.0.236/trunk@50341 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@23707 18797224-902f-48f8-a5cc-f745e15eee43
