Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "user story" issue template #220

Merged
merged 2 commits into from
Jul 22, 2024
Merged

Add "user story" issue template #220

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
185940c
Add initial "user story" template
danielnaab Jun 20, 2024
7e83d9e
Update .github/ISSUE_TEMPLATE/story.md
danielnaab Jul 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 64 additions & 0 deletions .github/ISSUE_TEMPLATE/story.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
---
name: Story
about: Suggest a user story for this product
title: ''
labels: story
assignees: ''
projects: ['GSA-TTS/17']
---

## Overview

As a _, I would like _, so that I can _.

## Context

*Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.*

- [ ]

## Acceptance Criteria

*Required outcomes of the story*

- [ ]

## Research Questions

- *Optional: Any initial questions for research*

## Tasks

*Research, design, and engineering work needed to complete the story.*

- [ ]

## Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

- [ ] Behavior
- [ ] Acceptance criteria met
- [ ] Implementation matches design decisions
- [ ] Documentation
- [ ] ADRs (`/documents/adr` folder)
- [ ] Relevant `README.md`(s)
- [ ] Code quality
- [ ] Code refactored for clarity and no design/technical debt
- [ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
- [ ] Code is reviewed by team member
- [ ] Code quality checks passed
- [ ] Security and privacy
- [ ] Security and privacy gates passed
- [ ] Testing tasks completed
- [ ] Automated tests pass
- [ ] Unit test coverage of our code >= 90%
- [ ] Build and deploy
- [ ] Build process updated
- [ ] API(s) are versioned
- [ ] Feature toggles created and/or deleted. Document the feature toggle
- [ ] Source code is merged to the main branch

## Decisions

- *Optional: Any decisions we've made while working on this story*
Loading