mirror of
https://gitlab.com/kelteseth/ScreenPlay.git
synced 2024-11-06 02:52:29 +01:00
35 lines
1.0 KiB
Markdown
35 lines
1.0 KiB
Markdown
|
<!---
|
||
|
|
Please read this!
|
||
|
|
|
||
|
|
Before opening a new issue, make sure to search for keywords in the feature
|
||
|
|
filtered by the "Feature" label:
|
||
|
|
|
||
|
|
https://gitlab.com/aimber/ScreenPlay/issues?label_name%5B%5D=Feature
|
||
|
|
|
||
|
|
|
||
|
|
Verify the feature you're about to submit isn't a duplicate.
|
||
|
|
--->
|
||
|
|
|
||
|
|
|
||
|
|
### Problem to solve
|
||
|
|
|
||
|
|
<!-- What problem do we solve? Keep it short like a TL:DR-->
|
||
|
|
|
||
|
|
### Further details
|
||
|
|
|
||
|
|
<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
|
||
|
|
|
||
|
|
### Proposal
|
||
|
|
|
||
|
|
<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
|
||
|
|
|
||
|
|
|
||
|
|
### What does success look like, and how can we measure that?
|
||
|
|
|
||
|
|
<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
|
||
|
|
|
||
|
|
|
||
|
|
### Links / references
|
||
|
|
|
||
|
|
/label ~Feature
|