Why is trackhistory/hierachy missing on my baseless merges on single WI/changeset?

Question

I use vs2013 and have made a simple tfs Tool, which - among other Things - do my baseless merges so I avoid using the tf command in a command prompt... :-)
The merges works fine but I now discover that my baseless merges loses track history and it looks as if I have persisted the changes directly in the targetbranch - even when they are merged (baseless) from another branch.
The code snippet where I loop thru the changesets in the WI which must be merged looks like this (and is quite self explaining):
foreach(varversionSpec
inchangeSets.Select(changeset
=> newChangesetVersionSpec(changeset.ChangesetId
   ItemSpecsourceItemSpec =
newItemSpec(source,
RecursionType.Full);
   GetStatus status = workspace.Merge(source, destination, versionSpec, versionSpec, LockLevel.None, RecursionType.Full, MergeOptions.Baseless);
----But why is tracking info in the changeset I persist not showing that it is merged from sourcebranch?

Answer 1

Hi Jesper,  
Thanks for your post.
If you manually perform the baseless merge on that same source item and target item, the tracking history will show correctly after merged?
Please provide a detailed example to descript your scenario, and please share your fully code snippet here.
To merge using TFS API, please refer to the example in this post:
https://social.msdn.microsoft.com/Forums/en-US/60852368-e5df-436b-8f45-ac0fa3b86f9f/tfs-api-example-requirement-merge-branch-by-using-c-and-tfs-api-and-hope-solve-conflict-using-api?forum=tfsgeneral.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.