scm code review export when only Change set linked to Workitem
![]()
vinitha dsouza (147●23●136)
| asked Nov 09 '17, 9:11 a.m.
edited Jan 11 '19, 3:49 p.m. by David Lafreniere (4.8k●7) Hello Team,
|
Accepted answer
![]()
Shashikant Padur (4.3k●2●7)
| answered Nov 12 '17, 10:15 p.m.
JAZZ DEVELOPER edited Nov 12 '17, 10:15 p.m. Exporting code review only makes sense when the target stream is set because you are reviewing the changes against that of the stream. The right thing to do is to show a message indicating that the code review has not been initiated or probably inform that the target stream is not set. vinitha dsouza selected this answer as the correct answer
Comments
In terms of implementation, the ICodeReview object is only created and associated to the work item once the Target Stream is set. The 'export code-review' command will try to find the associated ICodeReview objects of the workitem, and then dump JSON/XML data related to that (which includes the list of change sets the code review currently knows about). So that is why the output does not contain anything useful (because there is no Code Review yet). The Web UI indicates the requirements to start a code review:
-change sets associated to the work item -closed/completed change sets
-setting a target stream
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.