mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
Story template (#31340)
This commit is contained in:
parent
85993cbcb7
commit
33062791e4
1 changed files with 4 additions and 4 deletions
8
.github/ISSUE_TEMPLATE/story.md
vendored
8
.github/ISSUE_TEMPLATE/story.md
vendored
|
|
@ -19,9 +19,9 @@ It is [planned and ready](https://fleetdm.com/handbook/company/development-group
|
|||
| I want to _________________________________________
|
||||
| so that I can _________________________________________.
|
||||
|
||||
## Key result
|
||||
## Roadmap item
|
||||
|
||||
<!-- What quarterly key result (KR) does this story contribute to, if any? If it doesn't contribute to a KR, explain why it's being prioritized. -->
|
||||
<!-- Paste the roadmap item, from the current quarter's roadmap preview article, this story contributes to. Put "None" if it doesn't contribute to a roadmap item. -->
|
||||
|
||||
## Original requests
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ It is [planned and ready](https://fleetdm.com/handbook/company/development-group
|
|||
|
||||
## Context
|
||||
- Product Designer: _________________________ <!-- Who is the Product Designer to contact if folks have questions about the UI, CLI, or API changes? -->
|
||||
- Engineering DRI: _________________________ <!-- Who is the Engineer to contact if folks have technical questions? -->
|
||||
- Engineer: _________________________ <!-- Who is the Engineer to contact if folks have technical questions? -->
|
||||
|
||||
<!--
|
||||
What else should contributors [keep in mind](https://fleetdm.com/handbook/company/development-groups#developing-from-wireframes) when working on this change? (Optional.)
|
||||
|
|
@ -45,7 +45,7 @@ What else should contributors [keep in mind](https://fleetdm.com/handbook/compan
|
|||
- [ ] YAML changes: TODO <!-- Specify changes in the YAML files doc page as a PR to the 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. -->
|
||||
- [ ] REST API changes: TODO <!-- Specify changes in the the REST 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. Move this item to the engineering list below if engineering will design the API changes. -->
|
||||
- [ ] Fleet's agent (fleetd) changes: TODO <!-- Specify changes to fleetd. If the change requires a new Fleet (server) version, consider specifying to only enable this change in new Fleet versions. Put "No changes" if there are no changes necessary. -->
|
||||
- [ ] GitOps Mode UI changes: TODO <!-- Specify UI changes for read-only GitOps mode. Put "No changes" if there are no changes necessary. -->
|
||||
- [ ] GitOps mode UI changes: TODO <!-- Specify UI changes for read-only GitOps mode. Put "No changes" if there are no changes necessary. -->
|
||||
- [ ] GitOps generation changes: TODO <!-- Specify changes to results from the fleetctl generate-gitops command. Put "No changes" if there are no changes necessary. -->
|
||||
- [ ] Activity changes: TODO <!-- Specify changes to the Audit log page in the contributor docs. Put "No changes" if there are no changes necessary. -->
|
||||
- [ ] Permissions changes: TODO <!-- Specify changes in the Manage access doc page as a PR to the reference docs release branch. If doc changes aren't necessary, explicitly mention no changes to the doc page. Put "No changes" if there are no permissions changes. -->
|
||||
|
|
|
|||
Loading…
Reference in a new issue