What determines whether Permissions config'd or unconfig'd?
In my Process Config I set the Modify Work Items permissions at the Team Configurations level. I granted all Roles the permission to modify the Description field.
Now one of our Developers is saying he can't modify the field, even though he's a member of the team. Under the Team Configuration I have 2 timelines (New Development and Maintenance). I notice for New Development the Permissions is grayed out as Unconfigured. But under Maintenance the Permissions option is Bold and doesn't say Unconfigured. This seems to be the source of my problem because if I check the Modify Description Field box here the Developer doesn't have the problem. How can I disable or "unconfigure" the Permissions at this Timeline-level? I just want to set the permissions at the Team Configurations level. Note: I also noticed a couple of the Iterations under the Maintenance timeline have Permissions in Bold. Thanks, |
2 answers
Jared Burns (4.5k●2●9)
| answered Jan 27 '10, 4:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Wed, 27 Jan 2010 21:22:58 +0000, miwalker wrote:
In my Process Config I set the Modify Work Items permissions at the Team The editor is built on top of the process source XML, so this is what determines what the editor shows. When the editor shows that something is "unconfigured", this means that there is nothing in the XML which talks about that node. When it shows as bold but empty this means that there is an empty node in the XML - which means that the thing is configured but it's configured with no permissions. To verify and fix your problem, switch to the Process Configuration Source tab and look for a node in the XML which corresponds to the timeline you want to unconfigure. When you find it, you can just delete this element in the XML. This will unconfigure that timeline. For example, this specification says that the default role does not have any permissions to perform the operation "foo" in the "main" timeline: <process> <team> <permissions> <role> <operation> <action> </operation> </role> </permissions> <timeline> <permissions> <role> <operation> <empty> </operation> </role> </permissions> </timeline> <team> </process> If you were to delete the "timeline" element, then default role would fall back to having full permissions in all timelines. -- Jared Burns Jazz Process Team |
On Wed, 27 Jan 2010 21:22:58 +0000, miwalker wrote: In my Process Config I set the Modify Work Items permissions at the Team The editor is built on top of the process source XML, so this is what determines what the editor shows. When the editor shows that something is "unconfigured", this means that there is nothing in the XML which talks about that node. When it shows as bold but empty this means that there is an empty node in the XML - which means that the thing is configured but it's configured with no permissions. To verify and fix your problem, switch to the Process Configuration Source tab and look for a node in the XML which corresponds to the timeline you want to unconfigure. When you find it, you can just delete this element in the XML. This will unconfigure that timeline. For example, this specification says that the default role does not have any permissions to perform the operation "foo" in the "main" timeline: <process> <team> <permissions> <role> <operation> <action> </operation> </role> </permissions> <timeline> <permissions> <role> <operation> <empty> </operation> </role> </permissions> </timeline> <team> </process> If you were to delete the "timeline" element, then default role would fall back to having full permissions in all timelines. -- Jared Burns Jazz Process Team Thanks Jared, That solved our problem. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.