Bug 169376
| Summary: | Bug reopen doesn't have any way to cope with bug owner changes | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Suzanne Hillman <shillman> |
| Component: | Bugzilla General | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED WONTFIX | QA Contact: | Kevin Baker <kbaker> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6 | CC: | benl, ineilsen, taw |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-21 06:53:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Suzanne Hillman
2005-09-27 17:35:36 UTC
One easy way to handle this is to still display the "Bug Reassignment" section even for CLOSED bugs. Currently it is not displayed. This would allow someone with sufficient edit privileges to REOPEN the bug and also reassign the bug to the new default owner. We could even have the Reassign to default owner radio button automatically selected if the bug is closed. Sound sane? This assumes that someone reopening a bug would know that the problem exists. I think this is an invalid assumption, since it'd most probably be someone external reopening bugs. It needs to be done automatically... Another suggestion I was given is to check to see if the person currently assigned the bug on REOPEN is still a member of the Devel group, and if not, reassign to the new component owner. Well if the bugzilla account is disabled which I normally do if IS/IT informs me that someone has left, then it could just do a check for that before doing the reassignment. If all checks fail then it just leaves the assigned to alone. The you run into the problem where the current assigned to is no longer valid and the new one is not either, then we just punt. Shillman, not sure why we would need to check if the person is still in the 'devel' group, that is not relevant for all bugs. I think just checking to see if the account is disabled would be sufficient. > I think just checking to see if the account is disabled would be sufficient.
Agreed.
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. Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and therefore this feature will need to be implemented against the new release. Updating bug version to 3.2. 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 As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. Closing inactive bugs are part of Bugzilla cleanup. |