Commit 30fffd34 authored by Kristine Voigt's avatar Kristine Voigt
Browse files

Merge branch 'feature/#24-ticket-templates' into 'develop'

feat: add user stories and definition of done to ticket and merge request templates

See merge request subugoe/emo/Qviewer!11
parents ecaf999d 725a1f5c
Pipeline #138888 passed with stages
in 2 minutes and 22 seconds
# Bug
# Bugs
## Description
Just leave a short summary what the bug is about and where you came to notice it.
Just leave a short summary what the bug is about and in which context you noticed it.
Feel free to delete sections that doesn't suit the case you're dealing with.
### I expected the following to happen:
### I expected the following to happen
### On the contrary, I observed:
### On the contrary, I observed
......@@ -48,8 +49,8 @@ How much impact does this bug have on the product or further development?
Which version of the software did you use?
## Related tickets
## Related Tickets
Add related issues (if applicable).
Add related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)
# Feature Requested
# Feature Requests
## Description
Just leave a short summary what the feature is about.
## Use Cases
## User Stories
If you can, please provide use cases for this feature.
As (role of the user) I need (what has to be done) in order to (what I want to achieve with this feature).
## Classification
......@@ -17,6 +17,6 @@ Is this feature an enhancement of existing code or a completely new feature?
## Related Tickets
Add all related issues (if applicable).
Add all related issues.
/cc [Mathias Göbel](https://gitlab.gwdg.de/mgoebel), [Frank Schneider](https://gitlab.gwdg.de/schneider210), [Michelle Weidling](https://gitlab.gwdg.de/mrodzis)
# Bugfix
# Bug fix
Well, it seems that it is impossible to write software without bugs.
That's why we are really happy that you are here.
Thank you very much!
Please take a moment to help us include the purposed bugfix by filling out the following form.
Please take a moment to help us include the purposed bug fix by filling out the following form.
Feel free to delete sections that doesn't suit the case you're dealing with.
## Summary
......@@ -13,13 +15,23 @@ MR, tell us what you have done to achieve this goal.
## Related Tickets
Add all related issues and especially those to be closed.
Keep in mind that every bugfix branch needs an issue that properly describes the bug beforehand.
If your fix addresses something untracked, please open a ticket at first.
Keep in mind that every `bugfix` branch needs an issue that properly describes the bug beforehand.
If your fix addresses something untracked, please open a ticket first.
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [ ] Product Owner accepts the User Story
### Related
### Closes
## Changelog
* [ ] I added a statement to the CHANGELOG.
......
......@@ -2,13 +2,22 @@
We welcome every new feature to the upstream branch!
But at first we ask you to fill in the following information about your feature.
So please take a few minutes to make this great thing even better.
Please fill in the following information about your feature.
Feel free to delete sections that doesn't suit the case you're dealing with.
## Summary
This MR provides…
## Does the result of the MR comply to our "definition of done"?
* [ ] Unit tests passed
* [ ] Code reviewed
* [ ] Acceptance criteria met
* [ ] Functional tests passed
* [ ] Non-Functional requirements met
* [ ] Product Owner accepts the User Story
## Use Cases
If you can, please provide use cases for this feature.
......@@ -19,13 +28,12 @@ Shall we add your feature to the documentation?
* [ ] I've already did it!
* [ ] At least I added a headline to the documentation.
* [ ] Not applicable
### Function Documentation
* [ ] Of course I prepared all my functions with an appropriate documentation.
* [ ] Of course I provided all my functions with an appropriate documentation.
### Are There Parts of the Documentation We Have to Adjust?
### Are there parts of the documentation we have to adjust
* [ ] No.
* [ ] Yes, but I'd like someone else to do it.
......@@ -36,6 +44,7 @@ Shall we add your feature to the documentation?
Are we able to test this new feature?
* [ ] Yes, everything can be done via unit tests.
* [ ] Yes, you can test by following these steps: …
* [ ] No, it is not possible.
## Changelog
......
......@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
## [0.0.6] - 2020-05-29
### Changes
- add user stories and 'definition of done' criteria to issue templates (where applicable).
this should improve the development workflow for all stakeholders.
## [0.0.5] - 2020-05-20
### Added
......
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