Closed Bug 152899 Opened 23 years ago Closed 19 years ago

mid-air collision while marking a dup duplicates "this bug has been marked..."

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
Bugzilla 3.0

People

(Reporter: jruderman, Assigned: LpSolit)

References

()

Details

(Whiteboard: [blocker will fix])

Steps: 1. Load a bug. 2. Someone else adds a comment. 3. Try to mark the bug as a dup (in my case, without adding a comment). 4. Click through the "mid-air collision" page. Result: the "this bug has been marked as a duplicate of" line is duplicated (example: http://bugzilla.mozilla.org/show_bug.cgi?id=152860#c2)
Is this a regression? We're doing midair checks after setting FORM{'COMMENT'}, which then goes through to the hidden data
*** Bug 153711 has been marked as a duplicate of this bug. ***
It also happened to me with bug 178150...
*** Bug 276216 has been marked as a duplicate of this bug. ***
Flags: blocking2.20?
Flags: blocking2.18?
*** Bug 276216 has been marked as a duplicate of this bug. ***
This bug has been around pretty much forever, and although it's annoying, it's only a cosmetic issue. If someone patches it, I'll take it for 2.18, but I won't block release on it.
Flags: blocking2.20?
Flags: blocking2.20-
Flags: blocking2.18?
Flags: blocking2.18-
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.18
Depends on: 225221
Will be trivial to fix as soon as bug 225221 gets fixed. I already know how to do this. Note to self: append "this bug has been marked..." to the initial comment only when adding the corresponding comment to the original bug, that is: in the 'if ($duplicate)' block around line 1840 in process_bug.cgi instead of line 1055.
Assignee: myk → LpSolit
Target Milestone: Bugzilla 2.18 → Bugzilla 2.22
I won't have time to play with it before the 2.22 freeze
Target Milestone: Bugzilla 2.22 → ---
QA Contact: mattyt-bugzilla → default-qa
Status: NEW → ASSIGNED
Depends on: 353656
Whiteboard: [blocker will fix]
Target Milestone: --- → Bugzilla 3.0
Fixed by bug 353656
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.