mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
Update new-feature-work.md (#8580)
This commit is contained in:
parent
8ef9f805f5
commit
d436fdfe9f
1 changed files with 4 additions and 4 deletions
8
.github/ISSUE_TEMPLATE/new-feature-work.md
vendored
8
.github/ISSUE_TEMPLATE/new-feature-work.md
vendored
|
|
@ -25,7 +25,7 @@ TODO
|
|||
Why should Fleet work on this problem? How does this contribute to our reaching our strategic goals?
|
||||
-->
|
||||
|
||||
## Analytics
|
||||
## Measurement
|
||||
TODO
|
||||
<!--
|
||||
- How will we know that the problem has been solved or improved?
|
||||
|
|
@ -41,11 +41,11 @@ TODO
|
|||
3.
|
||||
|
||||
<!-- Things we tend to forget about -->
|
||||
- **Documentation** Do you want a guide written about this?
|
||||
- **Analytics** How are we going to measure usage and success?
|
||||
- **Documentation** Do you want a guide written about this? What things/aspects should we make sure is covered by the documentation?
|
||||
- **Analytics** How are we going to measure usage and success? Make sure engineering knows these need to be built.
|
||||
- **QA** Any special QA notes?
|
||||
- **Other depts.** Should other Fleet departments such as marketing, sales, CX be informed after this is shipped?
|
||||
- **Premium** Should this be a premium-only feature?
|
||||
- **Premium** Should this be a premium-only feature? If so, make sure to update the pricing page.
|
||||
|
||||
## Design
|
||||
### UI
|
||||
|
|
|
|||
Loading…
Reference in a new issue