Public Feature Pipeline issueshttps://git.wechange.de/code/public-feature-pipeline/-/issues2023-02-06T19:21:21Zhttps://git.wechange.de/code/public-feature-pipeline/-/issues/17How to write an Issue!2023-02-06T19:21:21ZHelmut Wolmanhelmut.wolman@wechange.deHow to write an Issue!This issue helps you to understand, how you can best write your Issue, so that we can easily understand it.
Just use the Following Template, or at least the headlines
Please write them in English!
Für alles, was als Problem, Bug oder...This issue helps you to understand, how you can best write your Issue, so that we can easily understand it.
Just use the Following Template, or at least the headlines
Please write them in English!
Für alles, was als Problem, Bug oder Feature-Wunsch erkannt wird, und mehr als einen Chat-Hinweis braucht (besonders wenn Diskussionen und mehrere Lösungsoptionen entstehen oder ein Arbeitsaufwand von mehr als 10 min) muss ein Issue im jeweiligen Git-Projekt angelegt werden! Dazu bitte folgendes Muster verwenden:
----
## User Stories
<details><summary> Why is this Feature/ Bug important? </summary>
#### Which Targetgroup has a Problem or would profit from this Solution?
> Who is using our Plattform for which purpose? z. B. As a user I ... want the search to find only results, that match my search term.
As a user I want to ...
#### What Purpose, additional Value or target does this feature have?
> What will be possible or easier with this solution and how can we measure it?
</details>
## Problem
### Steps to reproduce
> How one can reproduce the issue? Please provide links to test it and screenshots as proves - this is very important!!!
### What is the current bug behavior?
> What actually happens
### What is the expected correct behavior?
> What you should see instead
## Possible fixes
> What different options do you see as a solution? (Name them A, B, C... and rank them with the easiest first and say, which option you would prever) Please provide screenshots or links to other plattforms with better solutions!
### Implications
> What implications does this change have on the user experience other than the expected improvement? And what implication does it have on security, privacy or the speed of the plattform?
### Technical suggestions
<details><summary> How developers can solve it </summary>
#### Where in the code should be done some changes?
> Which Solution/ Possible fix was selected? Where do you have to edit things? What code and switches you should change?
#### How to track you time and document your work
> On which clockify milestone should you track your time (might be indicated in the description of the attached milestone) and where do you have to document your work?
</details>
<details><summary> Definition of Done (for development) </summary>
_DoD checkmarks can also be set, if requirement is not applicable for this feature_
- [ ] Unit/integration tests have been created
- [ ] Frontend and backend code have been separated
- [ ] Backend code has been refactored
- [ ] Inline and complementary documentation (README/GitLab Wiki) has been updated
- [ ] Link to merge request has been attached to the issue
- [ ] [Accessibility best practices](https://git.wechange.de/wechange/aktuell/redesign/-/wikis/accessibility) have been integrated
- [ ] [Security & data privacy best practices](https://git.wechange.de/wechange/aktuell/redesign/-/wikis/IT%20security%20and%20data%20privacy) have been followed
- [ ] [Sustainability best practices](https://git.wechange.de/wechange/aktuell/redesign/-/wikis/sustainability) have been followed
</details>
`/label ~"[Bug]" ~"[1Questions]" ~"[PO-Inbox]"`
`/assign @helmut.wolman`
Diese Issue-Vorlage sollte immer im Original geupdated werden: https://git.wechange.de/wechange/aktuell/template/-/issues/7