Closed Bug 627145 Opened 14 years ago Closed 14 years ago

Bugzilla doesn't detect mid-air collision when blocking flag is set

Categories

(bugzilla.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Honza, Unassigned)

Details

STR: 1) Open a page with a bug report e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=626909 2) Open the bug report page on another machine, change the blocking2.0 flag and commit the change (you can probably use even another flag). 3) Go back to the first machine, don't refresh the page, and post a comment to that bug. 4) Bugzilla doesn't detect the "mid-air collision" and so, the flag is overwritten to the previous value (that was still on the first machine). Honza
Custom field changes are correctly detected upstream. This is a bug with bmo customizations.
Assignee: create-and-change → nobody
Component: Creating/Changing Bugs → Bugzilla: Other b.m.o Issues
Product: Bugzilla → mozilla.org
QA Contact: default-qa → other-bmo-issues
Version: unspecified → other
Thanks for fixing this in advance! I managed to remove the flag three times (in two hours) for bug 626909, while others had to repeatedly set it again for me, ugh. Honza
the blocking2.0 flag is actually a custom field in bmo, not a flag. i'm unable to reproduce this issue with the bmo/4.0.
Whiteboard: bmo4.0-resolved
I just had the same problem in bug 638075 See: https://bugzilla.mozilla.org/show_bug.cgi?id=638075#c11 This time it was the Component field. Honza
Whiteboard: bmo4.0-resolved → [bmo4.0-resolved]
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
OS: Windows Vista → All
Hardware: x86 → All
Resolution: WORKSFORME → ---
Whiteboard: [bmo4.0-resolved]
Honza, try again now that bmo is 4.0?
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → WORKSFORME
Great, works for me now, thanks! Tested on a dummy bug report here: bug 653058 Honza
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.