| Summary: | Flags reverted without warning when updating comment | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Jonathan Earl Brassow <jbrassow> |
| Component: | Creating/Changing Bugs | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4 | CC: | agk, jmcdonal, rjoost |
| Target Milestone: | 4.4 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-18 00:50:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jonathan Earl Brassow
2013-10-22 16:51:08 UTC
bug 475802 looks similar, but it was CLOSED. The "mid-air collision" detection feature should catch this. From reading the other bug it appears that there was an intention to fix this in the upstream 4.4, but that either didn't happen or didn't make it into our version of the code. I need detailed instructions to reproduce this error, as I cannot do so. Using Firefox 25 (Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0), I did the following: 1) Open two firefox windows, and log in as two different users with necessary permissions to see and change the flags. 2) View https://bzweb01-devel.app.eng.rdu.redhat.com/show_bug.cgi?id=908450 in each window. 3) In one window change the four rhel flags, and submit the change. 4) In the other window, make a comment without changing the flags. 5) I received a midair collision page, as expected. See screenshot. (In reply to Jason McDonald from comment #2) > The "mid-air collision" detection feature should catch this. From reading > the other bug it appears that there was an intention to fix this in the > upstream 4.4, but that either didn't happen or didn't make it into our > version of the code. The upstream 4.4 change was included in Red Hat Bugzilla 4.4-3 (the first Red Hat Bugzilla 4.4-3 release we did) -- simon It is very likely that this upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=927570 which went live earlier this month is what fixed this problem. |