quality/blockerbugs
7
0
Fork 0
Code Issues 32 Pull requests 2 Projects 1 Releases Activity Actions

RFE: add nominating user to generated fedora-qa ticket, etc #293

New issue
Open
opened 2025-04-10 19:54:39 +00:00 by miabbott · 4 comments
miabbott commented 2025-04-10 19:54:39 +00:00
Copy link

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 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. - https://bugzilla.redhat.com/show_bug.cgi?id=2328530 - https://pagure.io/fedora-qa/blocker-review/issue/1838 _(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.
kparal commented 2025-04-16 12:11:01 +00:00
Owner
Copy link

When you propose a bug, you are informed that you should subscribe yourself:
proposal.png

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.

When you propose a bug, you **are** informed that you should subscribe yourself: [![proposal.png](/fedora-qa/blockerbugs/issue/raw/files/b8f80d0d6ae3db6884047f5a6a41397ec1cfe02851d9ab8c15dd0b59a001e064-proposal.png)](/fedora-qa/blockerbugs/issue/raw/files/b8f80d0d6ae3db6884047f5a6a41397ec1cfe02851d9ab8c15dd0b59a001e064-proposal.png) 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.
kparal commented 2025-04-16 12:11:53 +00:00
Owner
Copy link

Metadata Update from @kparal:

  • Issue priority set to: Low
  • Issue tagged with: enhancement
**Metadata Update from @kparal**: - Issue priority set to: Low - Issue tagged with: enhancement
miabbott commented 2025-04-16 13:03:01 +00:00
Author
Copy link

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! ❤️

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! ❤️
kparal commented 2025-09-03 12:14:21 +00:00
Owner
Copy link

Metadata Update from @kparal:

  • Custom field story_points adjusted to 5
**Metadata Update from @kparal**: - Custom field story_points adjusted to 5
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
staging
master
discussion_link_bz
feature/sync_in_admin_ui
flask_middleware_oc
feature/bugdeps2
kparal/selfref
1.16
1.15
1.14
1.13
1.12
1.11
1.10
1.9
1.8
1.7
1.6.1
1.6
1.5
1.4.1
1.4.0
1.3.1
1.3.0
1.2.1
1.2.0
1.1.0
1.0.0
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
0.6.1
0.6.0
0.5.0
0.4.15
0.4.14
0.4.13
0.4.12
0.4.4.11-1
0.4.4.11
0.4.4.10
0.4.4.7
0.4.4.6
0.4.4.5
0.4.4.3
0.4.4.2
0.4.4.1
0.4.4
0.4.3.6
0.4.3.5
0.4.3.4
0.4.3.3
0.4.3.1
0.4.3
0.4.2
0.4.1
0.4.0
0.3.0.3.4
t414-infrareviewfix
t414-proposalfix
0.3.0.3
0.3.0.2
0.3.0.1
0.3.0
0.2.5
Labels
Clear labels   
Closed As
Duplicate
 Closed with the reason of Duplicate

  
Closed As
Fixed
 Closed with the reason of Fixed

  
Closed As
Invalid
 Closed with the reason of Invalid

  
discussions
issues related to the blocker discussion system in pagure

  
easyfix

   
enhancement
a request for or implementation of an enhancement (not a bug fix)

  
task
issue that isn't a bug fix or enhancement but some kind of admin task

  
ai-review-please
Request AI review for a pull request

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
 This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
discussions
easyfix
enhancement
task
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/blockerbugs#293
No description provided.