65208 - Midair collision didn't happen.

Status: RESOLVED FIXED

(Bugzilla :: Creating/Changing Bugs, defect, P2)

Description

[Matthew Tuck [:CodeMachine]]

Just now [e-mail] should have got a midair collision on bug #24806 and
didn't.  He wanted to add to cc but I beat him to it by adding my name to QA and
putting in a comment.

He got an error message saying:

Only the owner or submitter of the bug, or a sufficiently empowered user,
may make that change to the qa_contact field.

Assumedly because he was not allowed to change back to blank which it was when
he loaded the page.

Is this check occurring before the midair collision check?  Or are we failing
the midair collision check?

This all happened around Friday January 12 2001 16:27 UTC if you want to check
the logs, about 10 minutes ago.

Comment 1

[Dave Miller [:justdave]]

moving to real milestones...

Comment 2

[Andreas Franke (gone)]

-> Bugzilla product, Changing Bugs component, reassigning.

Comment 3

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 4

[Felix Miata]

If you take an eagle eye to bug 54911 you should see that this just happened
there. I wouldn't have made comment #36 there @23:08 if Bugzilla had detected
the keyword and severity changes made @23:03, which followed my duping my own
bug 132477 @22:58. In effect, the absence of collision caused unnecessary spam.
IMHO, this bug should not be rated minor.

Comment 5

[Joel Peshkin]

Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.

Comment 6

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.

Comment 7

[Frédéric Buclin]

This bug still happen on tip.

Comment 8

[Frédéric Buclin]

Fixed in Bugzilla 3.1.3 by bug 412836.