Team Member Permissions should allow for more detail, would like them to edit some fields in Task
We have created custom fields in a task that we would like our developers to be able to edit. For example, a development task to develop a script, when they complete this task, we would like to have them update a custom field with the repository link and revision number.
-
Hi Ashley, You might be able to do this with a custom task field property. Edit the field in your administration and go to the Advanced tab. There is an Edit Permissions selector that defaults to the typical settings for most data fields, which is project manager only. You can select "Assignee" to allow an edit by any assigned resource or "Read" to allow an edit by any user with read access to the project.
0 -
Hi Wes - I reviewed this via a support ticket (#16529) and was told that the above suggestion will not work if the team member does not have permissions to edit tasks. This is why I have submitted the request, although perhaps a bug since what you describe above should not exist in the software if it does not work.
0 -
It could be a bug, but it won't override item-based permissions which always take precedent. For example, a project task can't be edited by anybody who is not designated as a project manager on the project, a scheduler on the project or a PMO manager in their user profile. The user who is not one of those three cannot edit the task scheduling, budget or assignment data fields even if they have full read, add, change and edit item-based permissions. The setting we've referenced here will now remove the protection of the edit based on the project role, but it still cannot override the item-based permissions.
So if your user you're using as your initial test scenario has read-only permission, check the item-based permissions to allow change and it will either work or we have a bug. In doing this you have not given them change permissions to any of those protected data fields for PMs, schedulers and PMO managers. That data is still protected within the project and task data fields.
0
Please sign in to leave a comment.
Comments
3 comments