One search function to identify repository workspaces of all members of the 1 project area we are in

The general use case behind this request is based on our activities on server cleanup (which is often recommended by IBM). Server Cleanup is done to reduce the amount of "active data" as well as to reduce the number of visible entries in several dialogs for the users.

We are trying to delete or archive all configurations, Team and Project Areas that are no longer in use. Especially temporary artifacts are in focus to be deleted (e.g. open changesets or Repository Workspaces).

You are right with your general tool related view on workspaces, but considering the usual way we are working, this idea and our use cases might be better understandable for you.

RWS are usually used for following activities:

• Working on content in a stream
• Rebuilding the content of a Snapshot (e.g. for bug analysis)
•  temporarily building up content of a future stream (test before setting up the stream)

 

A Project Area either represents a Project (really a single project with all relevant content included) or a Process Area in which single Projects are represented e.g. as Teams. In addition, a Project might reuse some content from another (Platform) PA. This representation of a Project is relevant when a Project ends and we want to get rid of all "live" data for this project - deleting temporary stuff, archiving content and TA/PA.

 

Given the above usage scenario, it should be able to cover ~95%-99% of cases with the following ideas of PA association of a RWS:

• RWS which (active) flow target(s) are pointing to a stream which is inside a PA that should be archived
• RWS that (only) contains components of the PA to be archived
  • RWS that contains components of the PA to be archived and another Platform PA
• RWS that is created from a Stream / Snapshot that is owned by the PA to be archived

 

In the end, we would need some criteria like the above mentioned easily to be used in e.g. a report or at least an API, that we can build the necessary reports and decide on the correct filter criteria to run a bulk delete in UI or through API calls.

The EWM Ideas Review board looked at this request and decided to keep it on the Backlog as an uncommitted candidate for a future release.

The EWM Ideas Review board looked at this request. Typically, workspaces are associated to repository and not project area. You can add components to your workspace from different streams across projects areas or even across repositories. Secondly, in principal administering workspaces is not an Admin activity, these are owned and managed by individual users (or may be owned by project area or team area in some cases). Therefore, we are unable to understand the request and need additional information to understand the use case better.

Hello, 

please see additional details regarding to our use cases: 

1) User is no longer in company

a) AEEE bulk re-assignment ( is this possible? - authorization missing to check)

b) AEEE Bulk delete ( working, we have the solution)

2) Project area archiving - and all workspaces have to be deleted - no idea for possibilities

3) Regular clean-up reminders - Admin overview for whole server (group all workspaces of a user also with each Project Area info) -> API also needed for a new ADMIN feature to be scripted internally / UI not helpful due to manual work overload