Hello.

In our company we use SourceTree as a Git Client for our self hosted Bitbucket DataCenter.

One of our repos is a very big one with probably millions of commits and many branches.

I've discovered that on the latest 3.4.31 when we go to History, Select Current Branch and then we click Jump to:Commit... and then we enter the commit hash, the first result is a commit close to the desired hash in date (example, Today 6 Jul I jumped to a commit from 6 May, but first I scrolled to a random commit in June and then I had to reuse the function to jump to my current commit).

Example, I searched for "94e97398b05994feb012dd874838f1631f647f74"
First jump to commit to "b6f73f24592c6391de986f7f37f8a07eaeba2446 "

Now I jump again

And I get my desired commit

This worked with only one jump before.