22f7a5bd02
A lot of feature requests are butchering the gherkin statement, so hopefully an example shows that the format and flow should be formatted as such. This format makes it very easy to see what the feature request is and why it is wanted.
15 lines
508 B
Markdown
15 lines
508 B
Markdown
---
|
|
name: Feature enhancement or request
|
|
about: Improvements or ideas for GriefPrevention
|
|
title: Name of feature goes here. No brackets, please.
|
|
labels: Add-on suggestion
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
**As** a player
|
|
**I want** to capture animals in a snowball
|
|
**Because** I wanna be the very best, Like no one ever was.
|
|
|
|
Here's how to increase your chances of your feature request being understood (and potentially considered for implementation): https://content.pivotal.io/blog/how-to-write-well-formed-user-stories
|