I did that by creating a Repository workspace that flowed from the stream on “jts_old” and selecting the Use another repository (“jts_new”) option.
Selecting a repository that is different from the flow target will create a distributed flow and cause components to replicate across servers. Initial replication may be a long process.

Having successfully created the repository workspace I then added a Flow Target to a brand new stream on “jts_new” and was then able to Deliver using the option to “Deliver component additions/removals as well as outgoing change sets and baselines”.

At no stage in this process did I have to provide any Work Item Associations.

That all happened a couple of weeks ago and “jts_new” now has a few components.

However, since then some changes have been made on “jts_old” that I would like to have on “jts_new”. I thought this would be relatively easy this time as it was only a few changesets and files and I could just do the same sort of thing as before.

I repeated the process of creating a Repository workspace that flowed from the stream on “jts_old” and selecting the “Use another repository (jts_new)” option.
I added the Flow Target (outgoing) to the same stream on “jts_new” that I had used before.

The “Pending Changes” view identified the handful of recent changesets as “Outgoing”.
(Note: these changesets were displaying the Work Item association that was used when they were delivered into “jts_old”).

But when I tried to Deliver I got error messages about “Missing work item” and “Assigned work items don’t meet requirements”, “The change set must be associated with a work item”.

Question : Why am I getting error messages about associated work items when I didn’t get anything like that when I did the initial copying a couple of weeks ago?
What am I doing wrong ?  I’ve got a feeling it’s something obvious.

Thanks

                Peter