If a bug exists against component A and a developer sets the pc ack flag to ?, and that component is already on the approved list, the bugbot sets the pm ack flag to +. If the component of the bug is then later changed to something that isn't already approved, bugzilla should set the pm ack flag to ? when changing the component. It doesn't and as a result we end up with a bug against a non approved component with the pm ack flag set to +. When I changed bug 249246 from openib to librdmacm is an example of how/when this can happen.
Hi Doug, are you reporting this issue against the production bugzilla bugzilla.redhat.com ,,, or against the new 3.2 bugzilla on partner-bugzilla.redhat.com ? Noura
The production bugzilla...I wasn't sure what version it was and just assumed it was the latest.
Red Hat Bugzilla is now using version 3.2 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.2.
Hi Doug, There isn't currently any mapping between the pm_ack flag and any bug field changes in bugzilla, flags gets manually set by bugzilla users who are authorized to do so, so should there be an automatic mapping? Is that a feature request by Product Management to be added to bugzilla? Noura
This is not a bug, so closing it, please reopen it if you would consider it a new feature request.