As far as I know, the Plastic 5.0.44 has added the merges to a History as a 2D tree view, but it doesn't add it to History view and it doesn't take into account the reverts (Revert to this revision) in both views.

Hi,

Are you using the latest 5.0 release?? Have you seen the improvements to item merge tracking there?

http://codicesoftware.blogspot.com/2013/11/plastic-scm-release-5044505-including.html

I think this fixes the issues you mention, correct?

http://www.plasticscm.net/index.php?/topic/1291-some-ux-issues/?p=12646
History and History as 2D tree are very useful features. However, there is a problem with those views. They do not show the real history of changes of the item as user may expect. The history view is actually a list of all revisions of that file, which is not the same, because the same revision could be used more than once and in more places. I mean, when using Revert to this revision, an old revision is checked-in again, but this information is not shown in the “History” because no new revision has been made. Similarly, when there was a merge (or a cherry pick) between branches, a file change was copied to another branch, but you don’t see this important thing in “History”. Again: because no new revision of that file has been made. History as 2D tree has both of these limits too. This leads to a big confusion among users – see these links for instance:

http://www.plasticscm.net/index.php?/topic/1741-merge-not-displayed-neither-in-file-history-nor-in-file-2d-history/
http://plasticscm.uservoice.com/forums/15467-general/suggestions/3950398-show-merges-in-file-history-and-2d-history (This suggestion is basically a subset of mine.)
http://www.plasticscm.net/index.php?/topic/1860-missing-file-history-entry-after-revert/
http://www.plasticscm.net/index.php?/topic/1939-file-revisions-and-tracking-them/

So my suggestion is add all these information to History views two. Frankly, I don’t see any usecase where somebody doesn’t want to see it.