User story template (#27293)

Add a "Contributor API changes" checkbox in the "Engineering" section.
This way we spec contributor API changes before we get to estimation.
This commit is contained in:
Noah Talerman 2025-03-19 17:04:05 -04:00 committed by GitHub
parent 1360862727
commit dea69de8d8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -56,6 +56,7 @@ What else should contributors [keep in mind](https://fleetdm.com/handbook/compan
### Engineering
- [ ] Test plan is finalized
- [ ] Contributor API changes: TODO <!-- Specify changes in the the Contributor API doc page as a PR to reference docs release branch following the guidelines in the handbook here: https://fleetdm.com/handbook/product-design#drafting Put "No changes" if there are no changes necessary. -->
- [ ] Feature guide changes: TODO <!-- Specify if a new feature guide is required at fleetdm.com/guides, or if a previous guide should be updated to reflect feature changes. -->
- [ ] Database schema migrations: TODO <!-- Specify what changes to the database schema are required. (This will be used to change migration scripts accordingly.) Remove this checkbox if there are no changes necessary. -->
- [ ] Load testing: TODO <!-- List any required scalability testing to be conducted. Remove this checkbox if there is no scalability testing required. -->