Ticketsystem (Gitlab) für Nutzer zur Kommentierung öffnen
Why is this Feature/ Bug important?
Which Targetgroup has a Problem or would profit from this Solution?
Who is using our Plattform for which purpose? We have some very active users on the plattform with a strong dedication to opensource and our cooperative.
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? For a better feature design, which really solves the users problems, it would be wise to involve them prio of the feature devolepment in the discussion about the issue.
Steps to reproduce
How one can reproduce the issue? Please provide links to test it and screenshots as proves - this is very important!!! Every user can open any of our public issues like this: #27 (Public is only this repository. No other is visible. As you can see here: https://git.wechange.de/wechange/aktuell if you open it in a browser, where you are not logged in https://git.wechange.de/wechange/aktuell)
What is the current bug behavior?
The register-Button redirects you to the login page https://git.wechange.de/users/sign_in?redirect_to_referer=yes#register-pane with no option for registration.
What is the expected correct behavior?
I would expect a formular which opens to enter my mail and choose a password to crate an account.
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!
A. We should allow the registration of new users in the general settings of our Git-Instance.
- New users would have only rights to comment in public projects
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?
- Nothing additional will be visible. Only public projects, which are visible know, stay visible.
- Guests dont have the write to edit the descriptions, nor to change lables, assignements or delete other comments
- You coudl expect some spam, but even on github, where everybody can comment, it basically never happens.
How developers can solve it
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?
- Helmut can not access the general seetings, so no more details for now.
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?