Description of problem: Committing changes to a stale view of bug 470387 did not result in a mid-air collision. Changes by others since last update were silently lost. See: https://bugzilla.redhat.com/show_activity.cgi?id=470387
This will need to be investigated further. Changing to ASSIGNED. Also reported here: https://engineering.redhat.com/rt3/Ticket/Display.html?id=30724
Fix committed to help with this issue. Further details on actual fix in https://engineering.redhat.com/rt3/Ticket/Display.html?id=30724 Dave
Reopening as this has not been fully fixed in some cases. Details from IRC: <dkl> sly: what i think is happening is, users who have request privs for a flag, but *not* grant privs, the '+' and '-' options do not display in the drop down for a flag so in this example, lillian has request rights so she sees the '?' and ' ' options only unless the flag is already set to '+', then it displays so if her page is not refreshing the options list for the flags on reload properly, she still only sees '?' even though you had already set it to '+' prior and then since the delta_ts timestamps line up properly, she does not get a midair collision screen but bugzilla happily sets the flags back to '?' sly: so in a nutshell my fix would be to show the '+' and '-' options in the drop down even though the user is not able to grant that flag sly: the backend code will catch the improper permissions later after the form is submitted so not a security issue <dkl> sly: the old 2.18 Bugzilla code displayed the options even though the user could not grant/deny a flag which is why I think this worked before. The new 3.2 code actually hides the options based on the users permissions
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.4.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can. Thanks Bugzilla Development Team
Is this still an issue? I haven't heard it reported in the 1½ years that I'm working in Bugzilla. -- simon
*** This bug has been marked as a duplicate of bug 475802 ***