Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Clarify role of main description vs. comments in github issue (#10613)

Browse source
This commit is contained in:
Mo Zhu 2023-03-20 15:44:08 -07:00 committed by GitHub
parent c4c5aae236
commit ec34f2f9da
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/product/README.md
View file

@ -40,6 +40,8 @@ Look here for more information about [Using Figma](https://fleetdm.com/handbook/
* During the product huddle meeting, record and address any feedback on the draft.
> As drafting occurs, inevitably, the requirements will change. The main description of the issue should be the single source of truth for the problem to be solved and the required outcome. The product manager is responsible for keeping the main description of the issue up-to-date. Comments and other items can and should be kept in the issue for historical record-keeping.
### Deliver
* Once your work is complete and all feedback is addressed, make sure that the issue is updated with