how can i prevent check in with code not associated to RTC workitem
if the code they want to checkin is not associated to RTC workitem, they are able to do checkins
We want to mandate the process, if code is not associated to work item, it shoudnt allow them to checkin
|
Accepted answer
Hi Ahmed,
Verifies that change sets have work item links and/or comments. The precondition can be configured to require change sets to have a comment or a work item/change request (OSLC link). If a work item is required, the owner and target iteration can be verified. Although it makes sense to constrain the work item owner and iteration in development streams, this requirement is not true of integration streams, since:
Regards,
Arun.
ahmed bayoumi selected this answer as the correct answer
Comments Operational behavior on check-in is not yet available. To be able to use operational behavior to control check in is planned for RTC 6.0.4.
In addition, there is not necessarily a change set before a check in, so I don't see that a pre condition to require a comment or a work item for check in would make any sense.
Advisors to require a work item or a comment is available for the deliver operation in all current versions of RTC.
|
