Bug on SourceTree for Windows - "Sort by" not using selection on refresh

Question

So I tried to set "sort by" to "path alphabetically" and it does sort everything by "path alphabetically" initially. But whenever it refreshes it sorts any files in a folder by "path reverse alphabetically"(the default). However it sorts files not in any sub folders by "path alphabetically", which is weird.

Is there a known fix for this? Or is this a bug/if it is, is there a bug report/ticket for this?

I just updated to 3.4.24 though I was having this issue in the previous version I had installed.

Step to replicate
1) Open a repo

2) add the following files. a.txt, b.txt, test/a.txt, test/b.txt, test/a/a.txt, test/b/b.txt

3) select any "sort by" option other than "path alphabetically" and then select "path alphabetically"

4) the files should be sorted like so, in the unstaged files section

5) refresh the repo(f5 or auto refresh)

6) the files now look like so

Note how /a.txt and /b.txt are in the correct order, but the files in test are in reverse alphabetical order. Also note how /test/b.txt is between the a and b folders, where as in normal "sort by reverse alphabetical" the folders would come first and then the files will come after.

Tomislav Tobijas · Answer

@Erich Schwarzrock I usually promote critical bugs/suggestions internally, within my company, to at least get a few more votes. It's not much, but I like to think it made a difference 😅

But thanks for sharing these here! If anyone else stumbles upon the same requirement/issue, they can simply vote for the linked items.

Erich Schwarzrock · Answer

I found 2 jira bugs for different versions, SRCTREEWIN-13077 and SRCTREEWIN-14153 . I'll leave a comment on them, though they haven't been touched in about a year when someone else left a comment on them. Not sure if there is any way to bring more light to this. As far as I can tell the only way to reach out to support is by filling a bug ticket, which has been done.

Tomislav Tobijas · Answer

Hi @Erich Schwarzrock ,

I couldn't find anything related to what you've described, and also no workaround for it.
You could take a second look at open bugs on JAC here.

What would be recommended in this case is to reach out to Atlassian Support. They should have dedicated staff members for Sourcetree who can try to replicate what you're experiencing, and if it's in fact an issue, someone will probably open a bug that you can track. (if they do so, feel free to share the link here)

Cheers,
Tobi