2023-10-05 Handbook/product#settled (#14270)

Once bugs have been settled, they should be removed from the drafting
board and moved into the 'to be scheduled' column of the bugs board so
that the PM knows they need to be prioritized into the sprint backlog.

---------

Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
This commit is contained in:
Isabell Reedy 2023-10-07 11:16:04 -04:00 committed by GitHub
parent f3daa2f0f0
commit e9c7d50a2f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -77,9 +77,9 @@ For external contributors: please consider opening an issue with reference scree
Once the draft has been approved, it moves to the "Settled" column on the drafting board.
Before assigning an engineering manager for [estimation](https://fleetdm.com/handbook/engineering#sprint-ceremonies), the product team should ensure the product section of the user story [checklist](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=story&projects=&template=story.md&title=) is complete.
Before assigning an engineering manager to [estimate](https://fleetdm.com/handbook/engineering#sprint-ceremonies) a user story, the product designer ensures the product section of the user story [checklist](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=story&projects=&template=story.md&title=) is complete.
> The story's designer is responsible for ensuring the checklist has been completed, the requirements section is consistent with the Figma, and the group engineering manager has been assigned.
Once a bug has gone through design and is considered "Settled", the designer removes the `:product` label and moves the issue to the 'To be scheduled' column on the "Bugs" board. The product manager then prioritizes the bug into the "Sprint backlog" and assigns the group engineering manager.
Learn https://fleetdm.com/handbook/company/development-groups#making-changes