How to handle multiple change requests in stream level
Kiran A (31●2●51)
| asked Sep 14 '18, 8:23 a.m.
retagged Oct 01 '18, 12:36 p.m. by Michael Afshar (701●4) Hello Team,
A - dev, B - systst, C - usrtst D - pdc
Here's My scenario, we are working simultaneously on multiple Change Requests. Let us assume My team is working on Change Request-1, Change Request-2, Change Request-3 parallelly (same file can be modified in all Change Requests). As our development completed we delivered our files to B stream and from B to C stream. Now our entire file is in C stream. Client requested us to deliver only Change Request-2 to D stream. In this case we are backing on how to deliver the changes that are worked for Change Request-2 (Change Request 1&2 should not be delivered).
Any Solution...
Regards,
Kiran
|
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 30 '18, 5:25 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 30 '18, 5:25 a.m. I assume you meant "change request 1&3 should not be delivered".
In RTC, this is called "merging change sets that contain gaps" (where the "gaps" are the change sets that you do not want to accept).
In a workspace that flows with (and is up-to-date with) D stream, accept Change-Request 2 into the workspace. Then follow the workflow defined in:
Then deliver the resulting change set to D 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.