When a user proposes a bug as a Blocker or a Freeze Exception, they should be added to the fedora-qa ticket and/or cc'ed on the proposed BZ. This will allow the user that submitted the proposal to be notified of progress on the status of the proposal.
As an example, I submitted my first bug as a Freeze Exception during the F42 cycle, but I didn't even know it was being voted on or that it was approved until I manually pulled up the bug a few days after the proposal and saw the activity on it.
(In this case I added myself to the CC list of the RHBZ after the FE was approved)
You could make the argument that I should have cc'ed myself on the BZ before submitting as an FE (since not all FAS accounts will have an RHBZ account attached). But it seems reasonable to expect to be added to the fedora-qa ticket where voting and discussion may happen.
When you propose a bug, you are informed that you should subscribe yourself:
The automatic CC was dropped here: https://pagure.io/fedora-qa/blockerbugs/c/665875e79b6c64c77f01d1496a10cae845cccb01?branch=develop https://pagure.io/fedora-qa/blockerbugs/issue/230
It would be nice to have it automatic again, yes.
Subscribing to the voting ticket is a nice idea, but as far as I know, Pagure doesn't support it. The person could be tagged in the ticket (that's not the same as subscribing to the ticket), but the ticket description gets updated by the bot regularly, so it could send recurring notifications. But perhaps there's a way to handle this.
Our general plan is that the voting ticket would be automatically linked in bugzilla (which the reporter should notice and could subscribe manually), but unfortunately it's not implemented yet.
Thanks for your suggestion. We'll try to look into it, if time allows.
Metadata Update from @kparal: - Issue priority set to: Low - Issue tagged with: enhancement
Thanks for pointing out that the user is prompted to add them to the CC list; clearly I missed that when I went through the process!
I think that is a decent solution until something more automatic could be implemented.
I appreciate your response and contributions to the Fedora community! ❤️
Metadata Update from @kparal: - Custom field story_points adjusted to 5
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/blockerbugs/issues/293
Please continue any further discussion there.
Log in to comment on this ticket.