Closed
Bug 97963
Opened 24 years ago
Closed 18 years ago
Error given if you try to move bug to another product when a midair has occurred.
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: CodeMachine, Unassigned)
References
Details
(Whiteboard: midair)
I just tried to move a bug to the new Bugzilla product. I got a message saying
a legal component was not set and to add to bug #20092. I won't do that because
it's too big already.
Anyway, I moved product, reassigned and added a comment. When I reloaded the
form, afranke had already beaten me to it.
So ... it looks like something is happening before it should ... because I'm not
getting a midair message here.
Reporter | ||
Comment 1•24 years ago
|
||
Just got this again. Just as I thought, you only need change product for this
to occur.
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
Updated•24 years ago
|
Whiteboard: midair
Comment 2•24 years ago
|
||
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.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 3•23 years ago
|
||
*** Bug 157085 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
See analysis in bug 157085. This is a fun one...
Comment 5•21 years ago
|
||
*** Bug 236384 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Target Milestone: Bugzilla 2.18 → Bugzilla 2.22
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
![]() |
||
Comment 6•18 years ago
|
||
I cannot reproduce the bug on Bugzilla 3.0. Probably this has been fixed thanks to our numerous changes in process_bug.cgi since Bugzilla 2.15.
Updated•18 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
![]() |
||
Comment 7•18 years ago
|
||
Do not reopen without explaining why you reopen it, and which version you used to reproduce the problem. Marking as WFM again. Be sure you tested on 3.1.2+.
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•