mirror of
https://github.com/fleetdm/fleet
synced 2026-04-27 16:37:55 +00:00
47 lines
1.2 KiB
Markdown
47 lines
1.2 KiB
Markdown
---
|
|
name: 🕸️ Website request
|
|
about: Propose a new feature or enhancement to fleetdm.com.
|
|
title: 'Request: __________________________'
|
|
labels: '#g-website'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
> **This request is expected to be doable in ≤1 sprint. It would be valuable even if nothing else ships.**
|
|
>
|
|
> It will be reviewed by the acting PM for the #g-website product group, and then hopefully [prioritized, drafted, and implemented](https://fleetdm.com/handbook/company/development-groups#making-changes).
|
|
|
|
## Goal
|
|
|
|
<!-- Describe the desired outcome -->
|
|
|
|
| User story |
|
|
|:---------------------------------------------------------------------------|
|
|
| As a _________________________________________,
|
|
| I want to _________________________________________
|
|
| so that I can _________________________________________.
|
|
|
|
## Changes
|
|
|
|
This issue's estimation includes completing:
|
|
- [ ] UI changes: TODO
|
|
- [ ] QA complete?
|
|
|
|
## QA
|
|
|
|
<!--
|
|
Make sure that someone verified each step outlined below before the associated PR is merged.
|
|
-->
|
|
|
|
### Manual testing steps
|
|
<!--
|
|
Add detailed manual testing steps for all affected user flows.
|
|
-->
|
|
|
|
1. Step 1
|
|
2. Step 2
|
|
3. Step 3
|
|
|
|
### Testing notes
|
|
<!-- Any additional testing notes relevant to this story or tools required for testing. -->
|
|
|