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

Update new feature work template (#8382)

Browse source 
- Update the issue template
This commit is contained in:
Mo Zhu 2022-10-21 07:09:54 -07:00 committed by GitHub
parent d0cfa7bbb3
commit 16d1ba80b7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 57 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

73
.github/ISSUE_TEMPLATE/new-feature-work.md vendored
View file

@ -2,38 +2,79 @@
name: 🎟  New feature work
about: Specify a planned, new feature in Fleet so that engineering can provide an estimation on the time required for implementation.
title: ''
labels: 'needs estimation'
labels: 'epic'
assignees: ''
---
### Goal
## Problem
TODO
<!-- Insert the user story or high level business goal. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit# -->
<!--
Motivate this feature by describing what is the user's problem.
- Who are the affected users?
- What is the current situation? Why does the current situation hurt?
- What are they doing right now to resolve this issue? Why is this so bad?
- How many users does this affect? How do you know? Share metrics or links to videos.
-->
### Figma
## Business Case
TODO
<!-- Insert the link to the feature's page in the Fleet EE (current) Figma file. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit#. Remove this "Figma" section if there is no link present in the google doc. -->
<!--
Why should Fleet work on this problem? How does this contribute to our reaching our strategic goals?
-->
### API wireframes
## Analytics
TODO
<!--
- How will we know that the problem has been solved or improved?
- What is the current state of the measurement?
- What measurements do you need to implement?
-->
## Requirements
<!-- Describe the required outcomes -->
TODO
1.
2.
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?
- **QA** Any special QA notes?
## Design
### UI
TODO
<!-- Insert a link to the draft PR that includes the proposed API wireframes to support the feature work. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit#. Remove this "API wireframes" section if there is no link present in the google doc. -->
<!-- Insert the link to the relevant Figma file. Remove this section if there are no changes necessary. -->
### How?
#### Frontend
### API
TODO
<!-- Describe the required frontend changes to support the feature work. Include screenshot's from the feature's page in Figma when appropriate. Remove the "Frontend" section if the feature work does not require frontend changes. -->
<!-- Specify what changes to the API are required.Remove this section if there are no changes necessary. -->
- [ ]
#### Backend
### CLI
TODO
<!-- Describe the required backend changes to support the feature work. Include screenshot's from the feature's page in Figma when appropriate. Remove the "Frontend" section if the feature work does not require frontend changes. -->
<!-- Specify what changes to the CLI are required. Remove this section if there are no changes necessary. -->
- [ ]
## Related
<!-- Insert related items such as child issues -->
### Child issues
Interface team
- TODO
Platform team
- TODO
Agent team
- TODO
Documentation
- TODO