@pbrobinson tried to propose https://bugzilla.redhat.com/show_bug.cgi?id=2017043 as an F36 Beta blocker using the app. The app just worked as normal and told him it was done. However, the bug had 'RejectedBlocker' in its whiteboard (from a previous proposal during the F35 cycle). This means the bug doesn't show up in the proposed blocker list - it's in a kind of conceptually-invalid limbo state (bugs should never be blocking a Blocker tracker but have RejectedBlocker in the whiteboard, it's not a state that makes any sense).
If someone tries to nominate a bug with RejectedBlocker in the whiteboard, the app should do something better. One option would be to just silently drop it from the whiteboard. Another would be to warn the user that the bug seems to have been rejected as a blocker already, ask if they're really sure they want to propose it, and wipe RejectedBlocker from the whiteboard if so. Another would be just to warn and tell the user to handle it manually, I guess. But whatever, it shouldn't do what it does right now.
Note I fixed this manually by clearing 'RejectedBlocker' from the whiteboard (you can see this logged at 2022-01-14 17:47:54 UTC in the bug comments). But the app left it in the bad state.
IMO what ever it does it shouldn't be silent, I think there's a couple of options: 1) Prompt the user it was rejected and ask them to confirm, at which point just clear RejectedBlocker 2) Make RejectedBlocker release specific and if it's for the same release reject it, if not add it 3) Reject it with a note along the lines of "Take it up with QE for further discussion" or similar
Thanks for the report. I'll make it a duplicate of my own 6 years old report (sigh...) and bump its priority: https://pagure.io/fedora-qa/blockerbugs/issue/40
I guess the easiest way to solve this is to clear selected tags from the whiteboard.
Metadata Update from @kparal: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/blockerbugs/issues/225
Please continue any further discussion there.
Log in to comment on this ticket.