Content
You are here:
[question] Changed Work Package settings are not saved
Added by Roger Helbling almost 10 years ago
Hello everybody
I have a problem and it is maybe only a configuration problem, but I can’t find it. :(
What I want:
A normal Member should be able to change the status and the progress of a work package, but not the start and stop date etc.
For that I had to remove in the role settings for the Member, that he can’t edit work packages.
Now the Member can only change the status and the progress in the work package settings. When I press save now, I get the response that it saved, but it didn’t.
Question:
Is this not possible like I want, or have I forgotten something to set?
If this is not clear enought, I can try to add tomorrow some pictures.
Kind regards,
Roger
Replies (10)
Hello Roger,
it’s unfortunately not possible to set edit permissions for individual work package attributes.
There is only the permission to edit a work package (which allows a user to edit all work packages).
Okay thank you.
I was a bit confused, because I have the possibility to select status and progress, but they don’t change when I press save.
On my server at home with the version 3.0.3 this works. That is also the reason why I thought it is a configuration problem.
Do you see a security issue, when I use the older 3.0.3 version? Because we need this “feature”.
Hello Roger,
that sounds indeed weird and I could not reproduce this behavior: For me, either all work package attributes can be edited or none.
Could you add a screenshot of this behavior? And an overview of the permissions the role has assigned which can edit only status and progress (permissions in the category “Work package tracking”)?
Thanks a lot,
Robin
We highly recommend to upgrade to the current version of OpenProject 3.0.x (3.0.17), since several important security fixes have been introduced since.
For a better overview of the security and bug fixe please refer to the release notes: https://www.openproject.org/download/release-notes/
I have setup a demo and it has the same behavior. The Version of this demo is 4.0.1.
I added a User to the Demo Project with the Role ‘Developer’.
The ‘Edit work packages’ settings gives the User permissions to change everything. If I remove this setting, the User has the settings you can see in the screenshot.
If the User now changes the Status and press save, he receives the green feedback that it is saved. But it is not.
Thanks,
Roger
#17927
I am struggeling with the same problem.
Any news?
Do I really have to give members the permssion “edit issue” to update the issue status? Although I already gave them permission to do so in the corresponding workflow?
Hello Johannes,
if you want all users to be able to edit work packages without adding them to the project first, you can set the permission “Edit work packages” for the role “Non member” in roles and permissions.
“Non member” is a role applied to all users who have an account on your instance (but possibly don’t have any additional permissions in the respective project).
Best,
Robin
Thank you Robin for your answer.
But I think you missunderstood my problem.
I have all team members in the project as “members”.
But I dont want them to edit the Due date and priority, etc of issues.
I only want them to change the issue status.
best regards
Ah, I see. Thanks for the clarification.
No, that’s unfortunately not possible. There is currently only a permission for all the work package attributes.
It’s not possible to allow users to edit certain attributes (e.g. status) but not others (e.g. start / due date, priority, etc.)
However, feel free to open a feature request (User Story) in the Wish List.
Cheers,
Robin