Commit 149cea23 authored by Thomas Löffler's avatar Thomas Löffler

Merge branch '380-update-issue-templates-for-features-bugs-tasks' into 'develop'

Resolve "Update issue templates for features, bugs, tasks"

Closes #380

See merge request !398
parents fe7d7eb3 a52cf25e
Pipeline #6408 passed with stages
in 6 minutes and 12 seconds
## What was the cause of the issue?
## Steps to reproduce
## Output of error log
## Add some screenshots
\ No newline at end of file
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label.
For Layout issues please use this tracker:
- https://git-t3o.typo3.org/t3o/t3olayout/issues?label_name%5B%5D=bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
(Summarize the bug encountered concisely)
### Steps to reproduce
(How one can reproduce the issue - this is very important)
### Example URL
(Add an Url where we can see the issue)
### What is the current *bug* behavior?
(What actually happens)
### What is the expected *correct* behavior?
(What you should see instead)
**Acceptence Criterias**
* [ ] Must be fullfilled
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
/label ~bug
/label ~ter
## What kind of feature do you want?
### Problem to solve
## What are the benefits?
<!--- What problem do we solve? -->
## Add some use case
\ No newline at end of file
### 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! -->
### 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 -->
**Acceptence Criterias**
* [ ] Must be fullfilled
### Links / references
/label ~feature
/label ~ter
## What do you suggest?
## Why?
## Add an use case
\ No newline at end of file
### Describe the task
<!--- What problem do we solve? -->
### Further details
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### 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 -->
**Acceptence Criterias**
* [ ] Must be fullfilled
### Links / references
/label ~task
/label ~ter
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment