Content
I decided to switch from freedcamp to openproject, but I can't set everything up correctly :(
I created an empty project, and one member (besides the admin) and added it to the project.
Created a couple of Tasks and assigned this user.
I need him to be able to change the status of the task (for example, put that it is in progress), and add notes and files in the comments to the task. But the user should not change the task itself (its description, priority, etc.)
Problem #1
Member cannot change Task status:
No settings in the workflow helped, even if I activate everything at all.
The only way a user can change the status is if I enable work package editing, but then he can edit everything in the task. Not only statuses.
How to configure so that the member can change the status of the task, but not the task itself?
Problem #2
Same thing with files. Member can add files to comments only if “Edit work packages” is enabled. Screenshot with disabled "edit" option:
Permissions. I enabled everything related to the files:
Here is an example with the option “Edit work packages” enabled:
How to configure so that a member can add files to the task, but not change the task itself?
Replies (4)
Hi Eugen Culicov,
Regarding problem 1:
There is no separation of allowing to update the status or the title and description. Once you are allowed to update the status you are always allowed to change the title and the description. In other words: Your scenario describes a missing feature in OpenProject.
Regarding problem 2:
If a user doesn't have the permission the edit a work package she also doesn't have the permission to add files/attachments. The logic is that adding a file is changing the work package. Adding a file to a comment actually adds it to the work package and then references it in the comment.
Regards,
Wieland
I encountered the same problem with the status change when I tried to set the demo OP where various types of clients can report the problem - but also accept it. This is naturally done by the status change in our previous issue management system. Clients do not have edit rights for the issue, but the status can be changed. Does it mean that in OP the client has to use comments to let us know that the issue can be closed?
This actually does not require permission, when there is a transition in the WF for the role+WP type, it should be possible to change the status.
About attachment limitations, I've learnt it in this forum post and it nearly made me panic. So the Client has to use some side channel (e.g. mail) instead of the issue management system to add more information to the issue - or we have to allow Edit to them? (But the latter is not acceptable for us.)
I'll try to find any related WPs for this and vote for them, but this is a gaping feature hole that makes it very hard to work with external reporters. :-(
(Funny enough, attachments can be added to forum replies.)
Hi Richard Richter,
What you are describing sounds to me liketypical "help desk" requirements:
I bet you would also like to have comments that are only visible to the staff, am I right?
OpenProject does not support those specifics. A use case that OpenProject supports is that you have a client with which you share a lot of information. So you simply create a project and give the client access to the project. Then in the project it is OK if the client can edit work packages etc. Private work packages are handled outside the scope of the work package.
I was pretty sure that we have an EPIC or FEATURE already somewhere but I cannot find it right now.
Heads up, the separate permission for status change is now part of released 13.2: https://community.openproject.org/work_packages/50849/activity