Stop associating work items with changesets?

It seems that RTC takes the last work item you marked as in progress and automatically associates it with any new changesets you create. This poses a problem since I may have marked an item in progress and added a comment, even in a different project area, yet when I create a changeset, it is associated.

I see in the Infocenter that you can "stop working", but that puts the status back to new. Is there any way to NOT automatically associate a work item to a changeset?

If the work item is marked as the current work item in the Eclipse client, it will associate the work item to new change sets. You'll see this on the right side of the bottom trim. If I remember correctly, the only way to stop this is to not mark work items as in progress because that is what causes the current work setting to change. The problem, as you found, is it changes the in progress status.

In 3.0, this was changed so that marking a work item as in progress doesn't set it as the current work. It also doesn't change the in progress status when you clear the current work item. So you'll have to work around it until upgrading to 3.0.

The semantics of this operation has evolved from release to release.
For example, in 3.0.1, you would use the "remove as current work" menu item.

Cheers,
Geoff

On 6/10/2011 11:08 AM, clselzo wrote:

It seems that RTC takes the last work item you marked as in progress
and automatically associates it with any new changesets you create.
This poses a problem since I may have marked an item in progress and
added a comment, even in a different project area, yet when I create
a changeset, it is associated.

I see in the Infocenter that you can "stop working", but
that puts the status back to new. Is there any way to NOT
automatically associate a work item to a changeset?

Great to hear that it's easier in RTC 3 and up. Thanks for your help.