Resouce Management within RTC
Is there any way to run reports of resources such as Repository Workspaces owned by a user? Along with access data such as last access and modified times?
Developers have a tendency to never delete things as administrators we need the ability to easily locate and remove work spaces and remind people to clean up.
Of more importance we have business rule which requires that the administration locate, preserve and review unfinished work when an employee leaves the company for any reason. The ability to easily locate resources by user would be very useful. We would rather not rely on naming conventions to find things.
Developers have a tendency to never delete things as administrators we need the ability to easily locate and remove work spaces and remind people to clean up.
Of more importance we have business rule which requires that the administration locate, preserve and review unfinished work when an employee leaves the company for any reason. The ability to easily locate resources by user would be very useful. We would rather not rely on naming conventions to find things.
One answer
You can find all repository workspaces and/or streams owned by a given
user with the RTC Eclipse client "Search -> Jazz Source Control" operation.
To find all work items owned by a given user, you can use the "Work
Items by Owner" report.
Cheers,
Geoff
On 10/16/2010 2:37 PM, mgr100 wrote:
user with the RTC Eclipse client "Search -> Jazz Source Control" operation.
To find all work items owned by a given user, you can use the "Work
Items by Owner" report.
Cheers,
Geoff
On 10/16/2010 2:37 PM, mgr100 wrote:
Is there any way to run reports of resources such as Repository
Workspaces owned by a user? Along with access data such as last
access and modified times?
Developers have a tendency to never delete things as administrators we
need the ability to easily locate and remove work spaces and remind
people to clean up.
Of more importance we have business rule which requires that the
administration locate, preserve and review unfinished work when an
employee leaves the company for any reason. The ability to easily
locate resources by user would be very useful. We would rather not
rely on naming conventions to find things.