I can't answer the questions about motivation, but I believe your guess
about the alternative is right. In order to "discard" a change from a
stream, you now discard the change from your workspace and replace the
component in the stream with the one in your workspace.

Jared Burns
Jazz Process Team


bill wrote:

I remember a while ago (like more than a year ago), it was possible to
show the history of a component in a stream via the Team Artifact
Navigator and then discard change sets from the history. This was a
nice feature in case you accidentally delivered a change set - you
could remove it from the stream without anyone noticing.

I tried to do this tonight and didn't see the action on the context
menu for the change set in the stream component's history. Was this
feature removed? If so, why? What's the recommended alternative?
Replace component in stream with the version of the component in your
Repository Workspace?

Jared is correct.

The motivation is that we wanted to emphasize the recommended approach to reverting a change which is to create a new change set which reverts the changes and builds on the previous change. This allows keeping a history of both changes, and makes it easier to merge and see the audit trail of all the changes. This is also what you are probably used to with all other SCM tools. The reverse action on a change set will help you with this.

Now if you want to actually remove all traces of the change set from your history, then you discard it from your repo workspace and replace the component in the stream with yours using the "Replace In <stream>" action from the Pending Changes view.

Jean-Michel
Jazz Source Control

And here is a link that puts images into Jean-Michel's words :-)

Discard a catastrophic change set from a stream

Chrix