we now search each list (dependson, blocks) to see if a bug number shows
up in each list. a bug can't be dependent upon and block the same bug.
also make it so you can't set a bug blocking or dependent on itself.
git-svn-id: svn://10.0.0.236/trunk@88020 18797224-902f-48f8-a5cc-f745e15eee43
When a bug is marked duplicate, the reporter should be added to the bug that it duplicated.
patch submitted by jake@acutex.net (Jake).
git-svn-id: svn://10.0.0.236/trunk@87145 18797224-902f-48f8-a5cc-f745e15eee43
is done for the dup id field, but not for the originating bug id.
now checks to see if the original bug id is valid as well, although i don't
understand how this could get corrupted in the first place
git-svn-id: svn://10.0.0.236/trunk@77486 18797224-902f-48f8-a5cc-f745e15eee43
midair collision happens which needs to generate text which needs to
look at the attachments table. Sigh.
git-svn-id: svn://10.0.0.236/trunk@62548 18797224-902f-48f8-a5cc-f745e15eee43
the difference between new comments and people copying stuff in from
old comments.
git-svn-id: svn://10.0.0.236/trunk@62534 18797224-902f-48f8-a5cc-f745e15eee43
bug queries can be run against it, so that these slow queries won't be
able to tie up the rest of the system.
git-svn-id: svn://10.0.0.236/trunk@61227 18797224-902f-48f8-a5cc-f745e15eee43
logged in. Since they haven't logged in, we don't know what they will
be allowed to do. And users who disable cookies tend to pretty often
not be logged in.
git-svn-id: svn://10.0.0.236/trunk@61203 18797224-902f-48f8-a5cc-f745e15eee43
"editbugs" and "canconfirm". People without these states are now much
more limited in what they can do.
For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them. Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page. But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.
git-svn-id: svn://10.0.0.236/trunk@61184 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
table. There is now a separate entry for each new long description,
rather than appending them all together in one big field.
git-svn-id: svn://10.0.0.236/trunk@58319 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
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".
git-svn-id: svn://10.0.0.236/trunk@56992 18797224-902f-48f8-a5cc-f745e15eee43
