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

Jump to bottom

re-introduce 'Acceptance Criteria' as part of the issue template #24

Merged
merged 1 commit into from
Mar 4, 2019
Merged

re-introduce 'Acceptance Criteria' as part of the issue template #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 13 additions & 2 deletions .github/ISSUE_TEMPLATE/task.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ about: Create a new Task

# Context

<!-- WHEN PROPOSED
<!-- WHEN CREATED
What is the issue that we are seeing that is motivating this decision or change.
Give any elements that help understanding where this issue comes from. Leave no
room for suggestions or implicit deduction.
Expand All @@ -15,13 +15,24 @@ room for suggestions or implicit deduction.

# Decision

<!-- WHEN PROPOSED
<!-- WHEN CREATED
Give details about the architectural decision and what it is doing. Be
extensive: use schemas and references when possible; do not hesitate to use
schemas and references when possible.
-->


# Acceptance Criteria

<!-- WHEN CREATED
Use standard vocabulary to describe requirement levels RFC-2119: Must-Should-May.

e.g.

1. The API _must_ support creation of wallets through a dedicated endpoint.
-->



---

Expand Down