Permissions when Modifying Work Items via Plan view
For purposes of this writeup, we have two roles: Team Member and Team Leader. The Team Leader role has full permissions. We would like to restrict Team Members from modifying the "Planned For" attribute on Work Items, only Team Leader can modify this attribue.
So, we set the Permissions under Team Configuration in Process Configuration as follows:
The "Modify work item's 'Planned For' attribute" is checked for Team Leader and unchecked for Team Member. "Modify Plan" is checked for both Team Leaders and Team Members.
Everything works fine when work items are opened and modified directly. However, when modifying work items indirectly through a Plan view (e.g. click on Priority or Complexity and choose a new value), the 'Save' button of the Plan becomes enabled and Team Members are unable to 'Save' the plan even though they have not modified the 'Planned For' attribute of any work item. It seems we need a new permission "Save plan except if 'Planned For' attribute of any work item was modified'. This seems like a 'Catch 22' and presents a UI design challenge. Any guidance or advise you can offer would be appreciated.
Thanks,
-Tim
So, we set the Permissions under Team Configuration in Process Configuration as follows:
The "Modify work item's 'Planned For' attribute" is checked for Team Leader and unchecked for Team Member. "Modify Plan" is checked for both Team Leaders and Team Members.
Everything works fine when work items are opened and modified directly. However, when modifying work items indirectly through a Plan view (e.g. click on Priority or Complexity and choose a new value), the 'Save' button of the Plan becomes enabled and Team Members are unable to 'Save' the plan even though they have not modified the 'Planned For' attribute of any work item. It seems we need a new permission "Save plan except if 'Planned For' attribute of any work item was modified'. This seems like a 'Catch 22' and presents a UI design challenge. Any guidance or advise you can offer would be appreciated.
Thanks,
-Tim
2 answers
First, you should make sure Team Member has the permission to modify plan
if you want Team Meber to be able to modify the plan. If Team Member has
been configured to not have the permission for "Modify work item's
'Planned For' attribute", then Team Member will be not allow to modify
this 'Planned For' attribute even from Plan View. In this case, Team
Member is able to modify other attributes of work item from Plan View.
if you want Team Meber to be able to modify the plan. If Team Member has
been configured to not have the permission for "Modify work item's
'Planned For' attribute", then Team Member will be not allow to modify
this 'Planned For' attribute even from Plan View. In this case, Team
Member is able to modify other attributes of work item from Plan View.
Hi Tim,
Below, when you say:
in what sense were Team Members unable to Save the plan?
For example, did they get an error in the Team Advisor
saying they were not allowed to do the save? If so, there
should have been information in the Team Advisor explaining
why not.
Or was that a typo, and you meant to say:
So it wasn't that you got a process error when you tried to
save, but rather that the "Save" button did not become enabled,
so you couldn't save your changes?
Please clarify.
Cheers,
Geoff
timothy.mulligan wrote:
Below, when you say:
the 'Save' button of the Plan becomes enabled and Team
Members are unable to 'Save' the plan
in what sense were Team Members unable to Save the plan?
For example, did they get an error in the Team Advisor
saying they were not allowed to do the save? If so, there
should have been information in the Team Advisor explaining
why not.
Or was that a typo, and you meant to say:
the 'Save' button of the Plan becomes *disabled* and Team
Members are unable to 'Save' the plan
So it wasn't that you got a process error when you tried to
save, but rather that the "Save" button did not become enabled,
so you couldn't save your changes?
Please clarify.
Cheers,
Geoff
timothy.mulligan wrote:
For purposes of this writeup, we have two roles: Team Member and Team
Leader. The Team Leader role has full permissions. We would like to
restrict Team Members from modifying the "Planned For"
attribute on Work Items, only Team Leader can modify this attribue.
So, we set the Permissions under Team Configuration in Process
Configuration as follows:
The "Modify work item's 'Planned For' attribute" is checked
for Team Leader and unchecked for Team Member. "Modify
Plan" is checked for both Team Leaders and Team Members.
Everything works fine when work items are opened and modified
directly. However, when modifying work items indirectly through a
Plan view (e.g. click on Priority or Complexity and choose a new
value), the 'Save' button of the Plan becomes enabled and Team
Members are unable to 'Save' the plan even though they have not
modified the 'Planned For' attribute of any work item. It seems we
need a new permission "Save plan except if 'Planned For'
attribute of any work item was modified'. This seems like a 'Catch
22' and presents a UI design challenge. Any guidance or advise you
can offer would be appreciated.
Thanks,
-Tim