---
# System prepended metadata

title: '[F {id} | {storypoints} SP] My Title'

---

# [F {id} | {storypoints} SP] My Title

<!-- While filling out each section also create Tasks * [ ]  !!--> 

### Description

<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->


### Acceptance Criteria

<!-- For example the saved Entity has an id, name, description etc. -->


### Tasks


### Proposal / Notes

<!-- How are we going to solve the problem? Give some real implementation ideas and specifications-->


/label ~"Type::Feature"
/label ~"Status::New"