2023 scraps from Fleet user story issue template (scrum, some content repurposed into fleetdm.com/handbook) For more info see https://github.com/fleetdm/fleet/pull/9375/files#diff-bed3ac553c0b018fe8820eab07bd3ec4b0423c6a149a178e59a80d5fa31b3c33

2023-scraps-from-fleet-user-story-issue-template.md

name	about	title	labels	assignees
🎟  Story	Specify an iterative change to the Fleet product. (e.g. "As a user, I want to sign in with SSO.")		story,:product

A user story is estimated to fit within 1 sprint, is QA'd, and drives independent business value.

User story

User story
As a _____________________,
I want to ___________________
so that I can ___________________.

Definition of done

This user story is estimated to include the following changes:

• User interface (UI): TODO
• Command-line interface (CLI) usage: TODO
•  
• …
•  
• REST API changes: TODO
• Database schema migrations: TODO
• Outdated documentation: TODO
• No changes to end user scope transparency?
• No breaking changes?
• Changes to paid features or tiers?
• QA complete?

Please read carefully and pay special attention to UI wireframes.

How?

Design

UI

TODO?

CLI usage

TODO?

Compatibility

REST API changes

TODO?

Database schema migrations

TODO?

User story
As a observer on the "Manage hosts" page,
I want to delete multiple hosts at the same time
so that I can delete many stale AWS instances that no longer exist.

ℹ️  Please read this issue carefully and pay special attention to UI wireframes.

---

name: 🎟  Story
about: Specify an iterative change to the Fleet product. (e.g. "As a user, I want to sign in with SSO.")
title: ''
labels: 'story,:product,#cx'
assignees: ''

---

This issue's remaining effort can be completed in ≤1 sprint. It will be valuable even if nothing else ships.

Goal

User story
As a _________________________________________,
I want to _________________________________________
so that I can _________________________________________.

ℹ️  Great user stories have clearly-defined changes.

Changes

This user story's estimation includes completing the following changes. It will be considered "done" when:

• Drafted, estimated, and scheduled for release.
• UI changes: https://fleetdm.com/handbook/development-groups#defining-done
• CLI usage changes: TODO
• ...
• REST API changes: TODO
• Database schema migrations: TODO
• Outdated documentation changes: TODO
• Transparency promise changes? TODO
• Breaking changes requiring major version bump? TODO
• Changes to paid features or tiers? TODO
• QA complete?

ℹ️  Please read this issue carefully and pay special attention to UI wireframes.