Split a Changeset.
Accepted answer
It is not currently possible to split a changeset after it has been delivered. An enhancement request is tracking this: Allow moving changes out of a delivered change set (59688). You can add a comment to the work item adding your specific use case or support of the enhancement.
Comments
Hi Laureen
Hi Erling,
A similar forum post from a few months ago discussed the same issue: https://jazz.net/forum/questions/83427/how-do-you-split-out-part-of-a-completed-change-set-into-a-separate-change-set. I don't know of a way to split the changeset programatically but maybe someone else does.
That is correct ... it isn't possible to split a change set if it has been completed (programatically or otherwise). Note that you can of course create a couple of new change sets, and have each change set contain the subset of changes that you want. But from RTC's point of view, these two new change sets will have no relationship to the original change set. (You can use the "patch" mechanism to help you create those two new change sets).
Okay. We are now working on a solution where we split the changesets before delivery into change sets containing each only one change. In this way a split will never come into question, and it is possible freely to pick changes for promotion into production.
It won't necessarily kill performance, but depending on how many changes are in the change set, it can harm performance. If your change sets usually have two changes, then splitting them all should be fine. If your change sets usually have 30 changes, splitting every change set into 30 change sets is likely to have a noticeable effect on the performance of some operations.