(Although I don't know if the contents of my initial changeset is relevant, I can add that my actual changeset 1000 was a change in what's the version of tfs are you using?
Tried on TFS 2015, branch a project and process two-way merge, but can't reproduce your issue.
No matter $North to $South, or $South to $North, there is no changes to merge.
It is not comprehensive but is intended to provide some visibility into key investments.
Most features are linked to a blog post and/or User Voice entry where you can learn more and comment.
These features and dates are the current plans at this time and are subject to change.
The “Planned Date” reflects when the feature will be available on VSTS and the “Server” column reflects when it will be available in TFS on-premises, if applicable.
The features timeline lists significant features delivered to Visual Studio Team Services and the corresponding version of Team Foundation Server.
Versions in the server column are linked to the appropriate download location.You can also view the build numbers for each version.Release management improvements – Azure deployments, release policies: Agent queue management Azure deployments Policies – Soft delete releases Policies – Retention of releases and builds Release definition authoring improvements – linked artifacts improvements Release – redeploy after success * TFS 2015 RTM has multiple build numbers, due to the componentized nature of its build and packaging process.The number of the installer, which will show up in Add/Remove Programs, is 14.0.23129.01.The number of the majority of the assemblies, which will show up in the TFS Administration Console, is 14.0.23128.00.Does anyone know if it is possible at all to completely discard a changeset, and also not having the discard itself appear as merge candidate in the other direction?