Content
View differences
Updated by Jens Ulferts 1 day ago
### Steps to reproduce
1. Go to the administration -> "projects" -> "new projects"
### What is the buggy behavior?
The dropdown for "Role given to a non-admin user who creates a project" shows users lacking essential permissions for a user having created the project. E.g. the seeded role "Reader" is listed.
If the project is created with such a role, subsequent steps cannot be taken as the permissions are lacking.
### What is the expected behavior?
1. Only roles having at least the following permissions should be options in the dropdown:
1. Edit project attributes - for filling out the PIR
2. Manage members - to add additional users (maybe?)
3. ~~Add work packages - for filling out the PIR~~
1. ~~View work packages is a dependency so it will be required as well~~
4. ~~Edit work packages (potentially if amends to the PIR need to be made)~~
5. ~~Manage file links - for uploading the PIR (not strictly necessary/depending on the configuration)~~
2. Add a caption explaining the need for the permissions
3. Ideally:
1. Show a notification if the currently selected role does not have the necessary permissions
2. Prevent or notify users from removing permissions from the selected role in the role's administration.
#### Out of scope
Migrating existing instances to safe roles.
1. Go to the administration -> "projects" -> "new projects"
### What is the buggy behavior?
The dropdown for "Role given to a non-admin user who creates a project" shows users lacking essential permissions for a user having created the project. E.g. the seeded role "Reader" is listed.
If the project is created with such a role, subsequent steps cannot be taken as the permissions are lacking.
### What is the expected behavior?
1. Only roles having at least the following permissions should be options in the dropdown:
1. Edit project attributes - for filling out the PIR
2. Manage members - to add additional users
3. ~~Add work packages - for filling out the PIR~~
1. ~~View work packages is a dependency so it will be required as well~~
4. ~~Edit work packages (potentially if amends to the PIR need to be made)~~
5. ~~Manage file links - for uploading the PIR (not strictly necessary/depending on the configuration)~~
2. Add a caption explaining the need for the permissions
3. Ideally:
1. Show a notification if the currently selected role does not have the necessary permissions
2. Prevent or notify users from removing permissions from the selected role in the role's administration.
#### Out of scope
Migrating existing instances to safe roles.