Currently, when looking at a review, it is hard to know the context of where an author intends to land this review. This information is crucial in an environment where a team is managing multiple release branches that will never converge, not just master.
Arcanist has this information available when someone types "arc diff <thing>". As I understand it, Arcanist find the merge base between <thing> and current HEAD and saves that to Phabricator (which can be fetched on a diff as the sourceControlBaseRevision of a diff). It would be nice if phabricator also stored the original <thing> string and exposed it in the UI and the differential conduit API. Another issue that we have is that we rely on the branch name to know which SDK to use to build our projects and we need this information to be able to build properly in Jenkins. We currently end up having to do a git branch --contains <merge-base> and build all the relevant branches that appear their after having patched with the changes from the review.