User story template

Description

Adding a user story template for client repos should help with #1 (closed) as user requirements don't have a direct template yet. Therefore, people tend to write issues about user requirements in free form. Adding a user story template would ask for a description in the format of: As a ..., I want ..., so that .... Then acceptance criteria must be provided to define a common ground on what functionality should do and lastly labels telling the reader what app it relates (using scoped labels).

### Story

<!-- Please provide a sentence descibing what the user wants to be added in the form of "As a ..., I want ..., so that ..." -->

### Acceptance criteria

<!-- A checklist overview of what the feature must be capable of. -->

- [ ] The date input must allow typing. 

<!-- Remove the labels that don’t apply. Please add the app label related to the story. -->

/label ~Feature ~"app::Example App" 

/estimate 1d

Requirements

• Must mention to add story.
• Must mention to add acceptance criteria.
• Must mention to must add app label where applicable.