Yeah, I also have a large hierarchy of projects and sorting by name is really bad. Sorting by name should behave like sorting by path first and then within a path sorting by project name. That would result in the sort order you desire and would work equally well if no project hierarchy exists (because then it would behave exactly the same as only sorting by project name). So order by "Path", "Name" would be nice to have.

Currently my sort by name result in something like

Company/apps/ Company/ Company/ops/a-project Company/apps/b-project Company/docs/c-project

which is super unintuitive. So I stick with default ordering, which is order by recently updated. This is likely better anyways because I have lots of projects with many being updated irregularly.

Project sorting is performed in database and path is derived from project hierarchy, which can not be used for sorting right now.

Maybe OneDev should add a field to record path and update this value of all affected projects whenever project hierarchy changes. May have some performance penalty though...

Makes total sense @robin but would be great for me and my OCD ;)

State changed as code fixing the issue is committed

State changed as build #2972 is successful