Commit 4955e9c3 authored by Lukas Riedel's avatar Lukas Riedel

Add Gitlab description templates from Utopia

Add slightly changed versions of
* bug report
* task
* MR from task

no  source files changed [ci skip]
parent 816ffa7f
(One-sentence description of what kind of bug you would like to report)
#### Summary
(Summarise the encountered bug concisely)
#### Steps to reproduce
(How can this be reproduced? If you can, point to specific files/configurations where the bug occurs)
#### What is the current _bug_ behaviour?
(More about the behaviour of the bug)
#### What is the expected _correct_ behaviour?
(Which behaviour would you have expected?)
#### Relevant logs, screenshots, files...?
(Anything that helps reproducing the bug)
<!-- Put very long log outputs within the <pre></pre> tags below -->
<!-- If this doesn't apply, delete the whole <details></details> block -->
<details>
<summary>Expand to see logs</summary>
<pre>
</pre>
</details>
#### Ideas how to fix this?
(Add them here, if you have any.)
/label ~bug
\ No newline at end of file
### Description
### Proposal
### How to test the implementation?
### Related issues
See #...
<!--
PLEASE READ THIS
Briefly explain __what__ should be changed and __propose__ how this can happen.
Adding pseudo code or diagrams would be great!
Additionally, you can:
- add suitable labels
- assign a milestone
- mention other issues
-->
### What does this MR do?
### Is there something that needs to be double checked?
### Can this MR be accepted?
- [ ] Implemented ...
- [ ] Added test to ...
- ...
- [ ] Pipeline passing
### Related issues
Closes #, # and #
<!-- For automatic closing, do not forget the commas between issue numbers-->
<!--
PLEASE READ THIS!
A Merge Request should be associated to a certain task or issue.
Its changes are supposed to be merged into the master branch.
Briefly explain __how__ you achieved the proposal of the task.
IMPORTANT: Make sure to set the merge request WIP if you are not finished yet.
-->
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