Clone a Role
Is it possible to clone a role in RTC 4? I'm after a role like Team Member, without the ability to deliver code (a read-only team member). I suppose I could write down all the permissions Team Member has an start from scratch with a new role, but thought I'd check on the cloning thing first. Didn't see that option in the Process Configuration for Roles.
Chris
Chris
4 answers
Hi Chris,
One way to do this might be to copy the XML code for an existing role in the "Process Configuration Source' tab.
For example, if I wanted to copy an existing role called 'Stakeholder' to be a new role called 'Cloned Stakeholder':
In the <role-definitions> ... </role-definitions> section of the 'Process Configuration Source', copy the exiting definition where name="Stakeholder" - for example, copying this line:
<role-definition cardinality="many" description="This role represents interest groups whose needs must be satisfied by the project. It is a role that may be played by anyone who is (or potentially will be) materially affected by the outcome of the project." name="Stakeholder" role-id="stakeholder"/>
and edit the copied code so that it has a different "name" and "role-id", for example:
<role-definition cardinality="many" description="Your description here" name="Cloned Stakeholder" role-id="cloned_stakeholder"/>
Then make a copy the XML definition for the original role-id in the <team-configuration><permissions>...</permissions></team-configuration> section, everything between:
<role id="stakeholder">
...
</role>
inclusively, and change the copied role-id value to match the new role-definition, for example:
<role id="cloned_stakeholder">
...
</role>
Then save that XML code. This worked well for me in 4.0.3. This kind of manual work is really error prone - so it's a good idea to save the XML before you start - and test this thoroughly before trying it in production.
I hope that helps,
John
One way to do this might be to copy the XML code for an existing role in the "Process Configuration Source' tab.
For example, if I wanted to copy an existing role called 'Stakeholder' to be a new role called 'Cloned Stakeholder':
In the <role-definitions> ... </role-definitions> section of the 'Process Configuration Source', copy the exiting definition where name="Stakeholder" - for example, copying this line:
<role-definition cardinality="many" description="This role represents interest groups whose needs must be satisfied by the project. It is a role that may be played by anyone who is (or potentially will be) materially affected by the outcome of the project." name="Stakeholder" role-id="stakeholder"/>
and edit the copied code so that it has a different "name" and "role-id", for example:
<role-definition cardinality="many" description="Your description here" name="Cloned Stakeholder" role-id="cloned_stakeholder"/>
Then make a copy the XML definition for the original role-id in the <team-configuration><permissions>...</permissions></team-configuration> section, everything between:
<role id="stakeholder">
...
</role>
inclusively, and change the copied role-id value to match the new role-definition, for example:
<role id="cloned_stakeholder">
...
</role>
Then save that XML code. This worked well for me in 4.0.3. This kind of manual work is really error prone - so it's a good idea to save the XML before you start - and test this thoroughly before trying it in production.
I hope that helps,
John