It's all about the answers!

Ask a question

Is there any easy way to locate within the entire repository a change set that is listed on a Work Item?


Jamie Berry (14012762) | asked Dec 20 '12, 3:38 p.m.
edited Aug 02 '16, 12:58 a.m. by David Lafreniere (4.5k7)
I know there is the Locate Change set command that allows you to check if the change set is in a particular stream or workspace, but if you wanted to see if a change set linked to a work item is located anywhere in the repository, is there an easy way to do it (either via the UI or via the API)?  We are developing a report to look at baselines and report on problem work items that either do or do not have all of their change sets in the baseline.  In cases like the one described in this post, where a change set has been discarded but not disassociated, the problem will come up as not completely included in the baseline.  Based on your description of the design intent of RTC, this is a correct report.  It would be nice if we could then take that change set that is missing and locate where it is sitting out in the repository or determine it isn't anywhere except hanging off the work item.

Thanks,

Jamie.

Accepted answer


permanent link
David Lafreniere (4.5k7) | answered Aug 02 '16, 1:18 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
edited Aug 05 '16, 7:47 p.m.
Just to add onto what Geoffrey already said... there's a wide range of ways to add 'objects' to the Locate Change Sets editor. I added the following information on a different forum post, but it can't hurt to put it all here too....

But to be specific to your question though, sounds like you want to add all streams in the repo by dragging and dropping the repository node from the Team Artifacts view to the 'Search Targets' section of the Locate Change Sets editor)... There is no 'one-click' way to find EVERY stream/repository workspace/snapshot/baseline that contains a selection of work items, having that easily searchable for all users might cause a performance hit on the server. Also, in most use cases we identified in the past, users generally have a 'sense' of what they want to search in (or where), so the flexibility explained below helps them with this...)
 

The most useful feature (for me at least) to add relevant search targets is to click on the green "+" icon in the 'Search Targets' menu, and select "Add workspace and flow targets shown in the Pending Changes view'; or you can select 'Add streams from project and team areas that I am a member of'.

Also, one of the best ways to 'save' and 're-use' a random or mix selection of Locate Change Sets [LCS] 'objects' is to put them in the favorites folder in the Team Artifacts view, then drag and drop the selection into the LCS editor when needed in the future...

Here's a listing of different ways to add 'objects' to the LCS editor:  

Ways to add Work Items:  
-Since RTC 4.0, you can drag & drop a selection of work items from various places in the UI (ex: The "Work Items" view, or from work items in the favorites folder in the Team Artifacts view)  
-Since RTC 4.0, you can drag & drop a work item query from the Team Artifacts view. This will automatically run the query and add the work items. 
-The work item picker dialog now allows multi-selection. Added in RTC 6.0.3 S5. 

Ways to add Change Sets:  
-Since RTC 4.0, you can drag & drop a selection of change sets from various places in the UI (ex: The "Pending Changes" view, "History" view, "Search" view, etc.)  

Ways to add Streams/Workspaces/Snapshots/Baselines/Builds:  
-Since RTC 4.0, you can drag & drop a selection of streams/workspaces/snapshots/baselines from various places in the UI (ex: The "Pending Changes" view, "History" view, "Search" view, "Team Artifacts" view favorites folder, etc."  
-You can also drag & drop a selection of team area nodes from the "Team Organization" view, which will add all streams owned by those team areas.  
-You can also drag & drop a selection of project area nodes from the "Team Artifacts" or "Team Organization" view, which will add all streams owned by those project areas and all child team areas.  
-You can drag & drop a repository node from the "Team Artifacts" view. This will show a confirmation prompt, asking if you want to add all streams in the repository.  
-You can drag & drop a selection of build results. This will add their corresponding build snapshots.
-You can open the Locate Change sets editor directly on releases (shown on the "Releases" tab of the Project Area editor). This will add the corresponding build snapshots. 
-The snapshot picker dialog allows multi-selection. Added in RTC 5.0.2. 
-The stream/workspace picker dialog allows multi-selection. Added in RTC 6.0.2.
Ralph Schoon selected this answer as the correct answer

One other answer



permanent link
Geoffrey Clemm (29.6k23035) | answered Dec 22 '12, 11:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In 4.0, the "Locate change-set" function has been significantly enhanced to allow you to specify both multiple change sets (or multiple work items) to be searched for, and to specify multiple streams/workspaces to be searched.  Have you tried this enhanced form of the Locate command to see if it gives you what you need?

Your answer


Register or to post your answer.