If you are using UCM, then all of the new versions created in ClearCase
for a given sync request will be associated with a single new ClearCase
activity which is the "change-set" associated with that sync request.

But this is at the granularity of the "sync operation", not at the
granularity of an individual Jazz change-set. It acts very much like a
UCM "deliver activity", where one activity is created for a given
"deliver" operation, even if many activities are being delivered.

There are several reasons for this:
- the directory versioning models for Jazz SCM and ClearCase are
different, so you cannot map a Jazz SCM directory version to a ClearCase
directory version, or vica-versa.
- there might be a large number of intermediate versions in the
change-set, and recreating them all could incur a prohibitively
expensive performance cost
- when only some of the files in the change set are being synchronized,
the change-set could not be carried over intact.

Cheers,
Geoff

w_t_roberts wrote:

I'm trying to work out how to use Team Concert for my development
teams around the world, but still bring their work back into the
"mother ship".

Looking at the online docs, the ClearCase connector overview says:
Change sets created in Jazz source control are checked in to
Rational ClearCase as new versions. New versions created in Rational
ClearCase are committed to the ClearCase Synchronized Stream. .

The wording here is describing different objects, which makes me
wonder if the connector represents the change sets in any way at all.
The phrase "new versions" refers to individual entities, but
"change set" is a collection of versionable entities.

What I would really like is for the result of doing both the ClearCase
and ClearQuest synchronisation of a Jazz work item with an associated
change set to give me a ClearQuest object which is associated with a
ClearCase activity that identifies the versions resulting from
synching the changeset.

Is that possible?

William