Content
View differences
Updated by Max Mutzge over 5 years ago
As an OpenProject user
I want to only see options I'm allowed to access and edit in a project
so that I can clearly understand what works and what doesn't and to avoid confusion.
As an OpenProject administrator
I want users to have as limited options seemingly(!) available as possible
so that they can concentrate on their work.
### Expected behavior
Removing permissions for a role in the administration leads to removed visible options in the project settings. Consistent behaviour of the effects of removing pr granting permissions.
**If this permission is removed this should happen in the project settings:**
a. _Select project modules_: Modules is hidden
b. _Manage versions_: At least button "close completed versions" is hidden
c. _Select types_: Work packages types is hidden
d. _Edit project_: Depending on what this is meant to do:
1) Hide project settings completely, or
2) Hide Project information
**This already works for:**
\-_Create subprojects_: button is removed
\-_Copy projects_: button is removed
\-_Manage overview_: Can't edit overview
\-_Manage members_ (while keeping _View members_): option to edit and delete is removed
### Current behavior
Cases a., b., c.: Options in project settings are not hidden; when trying to edit \[Error 403\] is shown (See also #35441)
Case d: If _manage versions_ is ticked, module Project settings is shown nevertheless. If nothing is ticked module Project settings is not shown.
### Conclusion
* hide all settings options a user has no permission to edit
* make effect of removing the _Edit projects_ permission consistent (it should either remove the whole project settings module or all other permissions should be able to override it, not just _manage versions_)
I want to only see options I'm allowed to access and edit in a project
so that I can clearly understand what works and what doesn't and to avoid confusion.
As an OpenProject administrator
I want users to have as limited options seemingly(!) available as possible
so that they can concentrate on their work.
### Expected behavior
Removing permissions for a role in the administration leads to removed visible options in the project settings. Consistent behaviour of the effects of removing pr granting permissions.
**If this permission is removed this should happen in the project settings:**
a. _Select project modules_: Modules is hidden
b. _Manage versions_: At least button "close completed versions" is hidden
c. _Select types_: Work packages types is hidden
d. _Edit project_: Depending on what this is meant to do:
1) Hide project settings completely, or
2) Hide Project information
**This already works for:**
\-_Create subprojects_: button is removed
\-_Copy projects_: button is removed
\-_Manage overview_: Can't edit overview
\-_Manage members_ (while keeping _View members_): option to edit and delete is removed
### Current behavior
Cases a., b., c.: Options in project settings are not hidden; when trying to edit \[Error 403\] is shown (See also #35441)
Case d: If _manage versions_ is ticked, module Project settings is shown nevertheless. If nothing is ticked module Project settings is not shown.
### Conclusion
* hide all settings options a user has no permission to edit
* make effect of removing the _Edit projects_ permission consistent (it should either remove the whole project settings module or all other permissions should be able to override it, not just _manage versions_)