If you set the role "Issue Reporter" as default role in a project and the user has only the authorization of the default role, he cannot create an new issue.
Reproduce:
Role Configuration
Group Configuration: Any "Not-Administrator"-Group
User: "Heinz" (The user has the default role "Issue Reporter" (configuration of role shown in screenshot) for the shown repository and got a "Not-Administrator"-group.)
Step 1: Login with User "Heinz"
Step 2: Click on a project (User only got "Manage Issue" permissions in the role, so he gets forwarded to the issue-management.)
Step 3: Click on the blue "+"-Button
Step 4: Errorpage opens
Even if the user is explicitly set the role "Issue Reporter" via "Authorization", the error appears.
Expected behaviour:
Open a "new issue" dialog
Additional Notes:
We don't use the Mail-Settings. I am not 100% sure if this is a bug in the source code or if I have configured it incorrectly.
Through further trail error tests, I was able to classify the problem more precisely. It seems to be related to the code permissions in some way. With the following role configurations I could not reproduce the error.
Enviroment:
OS: Linux 4.19.0-5-amd64, amd64
JVM: OpenJDK 64-Bit Server VM 1.8.0_292, AdoptOpenJDK
Total Heap Memory 3180 MB
Used Heap Memory 434 MB
Heap Memory Usage 13%
User: root
Version: 4.3.3
(Installed as system-service)
I think your work is great and I will continue to use and support OneDev! Maybe the problem is found and can be fixed!
Bug (short)
If you set the role "Issue Reporter" as default role in a project and the user has only the authorization of the default role, he cannot create an new issue.
Reproduce:
Role Configuration
Group Configuration: Any "Not-Administrator"-Group
User: "Heinz" (The user has the default role "Issue Reporter" (configuration of role shown in screenshot) for the shown repository and got a "Not-Administrator"-group.)
Even if the user is explicitly set the role "Issue Reporter" via "Authorization", the error appears.
Expected behaviour:
Open a "new issue" dialog
Additional Notes:
We don't use the Mail-Settings. I am not 100% sure if this is a bug in the source code or if I have configured it incorrectly.
Through further trail error tests, I was able to classify the problem more precisely. It seems to be related to the code permissions in some way. With the following role configurations I could not reproduce the error.
Enviroment:
(Installed as system-service)
I think your work is great and I will continue to use and support OneDev! Maybe the problem is found and can be fixed!
With best regards