Welcome to the Jazz Community Forum
RTC Is there a way to easily see all the files changed due to a workitem (eg defect)?
Hello,
Is there an option to easily identify the list of unique files modified as a result of a work item via the RTC WEB?
For example:
A defect was raised and 10 different files needed to be modified as a result of that defect.
The files are updated and upon examining the work item via the WEB, the change sets are visible, but unless a user clicks on each it is rather difficult to get a total list of unique files as a result of the defect. This makes it rather difficult when verifying that a defect has been resolved, particularly if the files are documents.
Thanks,
-Angela
Is there an option to easily identify the list of unique files modified as a result of a work item via the RTC WEB?
For example:
A defect was raised and 10 different files needed to be modified as a result of that defect.
The files are updated and upon examining the work item via the WEB, the change sets are visible, but unless a user clicks on each it is rather difficult to get a total list of unique files as a result of the defect. This makes it rather difficult when verifying that a defect has been resolved, particularly if the files are documents.
Thanks,
-Angela
Accepted answer
In the Eclipse and Visual Studio clients, you can multi-select the change sets in the Work Item links tab and select "Open" (Eclipse) or "Open in Change Summary" (Visual Studio).
This will open the selected change sets in the Change Summary View which will show all the files affected across the change sets.
Unfortunately this is not available from the web UI.
See this article: https://jazz.net/blog/index.php/2012/10/11/reviewing-code-changes-with-rational-team-concert/
This will open the selected change sets in the Change Summary View which will show all the files affected across the change sets.
Unfortunately this is not available from the web UI.
See this article: https://jazz.net/blog/index.php/2012/10/11/reviewing-code-changes-with-rational-team-concert/
One other answer
My assumption is, in the scenario that was used to implement RTC, you have a defect and then you fix the files you need to fix. Once they are fixed, test are commenced and run. When the tests succeed, and everyone agrees, the defect is resolved. You don't know the files that have to be changed up front. Usually no one could tell, "we need to fix file 1,2,3 and 4" and seeing that there are some changes to those files could judge that the defect is resolved. It is quite the other way around.
If you have a defect and that is resolving a problem, and you want to know if the change sets associated are in a stream or workspace, you can do so from the Eclipse UI by selecting 'Locate Change Sets'. In the search dialog you can select the streams to look into and it would tell you, if the change sets are there.
If you have a defect and that is resolving a problem, and you want to know if the change sets associated are in a stream or workspace, you can do so from the Eclipse UI by selecting 'Locate Change Sets'. In the search dialog you can select the streams to look into and it would tell you, if the change sets are there.