We have a requirement for a duty service engineer to be able to access anyones checked in (repository) workspace so that out of hours support, if escalated, can attempt to address resolve the issue.

We know that an administrator can take ownership of a workspace. However, we'd rather not give administrator privileges to all who may be on duty, which is essentially all the team.

If there another level of authority/privilege that would provide a similar result.

What kind of access do you want to the workspaces? Anyone can collaborate with another user's workspace to accept changes. The change sets must be closed in order to accept or you can accept as a patch to create a new change set.

The answer is pretty straightforward.

If the engineer has not checked in the changes, then those changes only
exist on disk (in the engineer's RTC client "sandbox"), so the only way
to see those changes is to get access to the disk containing those files.

If an engineer has checked in the changes, then they have been saved to
the RTC repository, and anyone with read access to the component
containing the changes can see them (even if the workspace was a private
workspace, you can still see the changes by searching for change sets
owned by the person making the change).

If the engineer has "completed" the change sets, then you can just
accept them into a workspace. If the engineer has not completed the
change sets, then you can still accept the changes into a workspace, but
in the form of a "patch" (RTC will create that "patch" for you).

Cheers,
Geoff

On 3/7/2011 9:53 AM, kbowkett wrote:

In the environment we work within, we need the ability to access in
flight changes that are made by another individual who has gone off
sick. For example, imagine servicing a product and engineer A is
assigned a Sev 1 problem to resolve for the customer. They spend 3 or
4 days diagnosing and working the problem before going of sick
mid-flight (or worse overnight the problem goes crit sit). The duty
service engineer (so our of hours) or colleagues may have to pick up
the pieces.

Today, using the service environment provided by IBM, the engineers
can reassign to anyone else within the same team.

We want to ability to do this without having to have full on
repository admin permission.

It might be easier to have a discussion about this over the phone
rather than by the forum.