these are the advanced features that might help

https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests

I think the closest one is using Labels and sorting by date

If you organize your issues into a GitHub Project list view, you can sort by the issue title.

Can this question be voted as a feature request?
Or can I branch and pull this functionality to GitHub myself somewhere?

This feature is very much needed. I'm surprised that github always implements complex, "clever" sorting methods but almost never alphabetical sorting. It took years until org repos could be sorted alphabetically, and the order doesn't even stick.

If we sort by name, searching becomes easier (searching in a sorted list is log n and requires less attention that searching in a list that is not alphabetically sorted). Also, since we can customize the names at will, it gives us the ability to customize the order.

Please add this - sorting by title seems like a fairly basic feature and hopefully easy to implement

I'd also like to pitch in on this. I understand can probably sound odd to most - who's sorting their bugs alphabetically??

There's a few reasons this is helpful in the main area, and not just in our personal project spaces, where in we can opt to do that via a 'view'. It's not for every repo out there, but for ones that have any sort of naming convention at all, it's helpful.

It probably doesn't make as much sense when you have >1000 (open) bugs or so, but smaller projects would benefit from having such a naming convention. Exactly what this convention comes down to really varies by project in my experience. It's good to have some flexibility here:

I do something like this, though this is just an example - the first could be location or type, with a possible second attribute to further organize the order.

GAMEPLAY: Level 1 - [bug title]
PAUSE: Settings - [bug title]

or

DOCS: contributing.rst - [topic to add]
REPO: conf.py - [some issue with the config]

Then I use labels for issue severities (A, B, C, 1, 2, 3), closure type (dupe, won'tfix), hold type (more info needed, more testing needed), regression concerns (reopened), and marking things that are 'requests' to consider. These labels can accumulate as mutable and coloured information below the bug, keeping its title immutable:

Labels are a bit subjective, whereas it's not subjective or subject to change where the bug is located or what type it is. (Other projects might have other objective realities they want to reflect or enforce in their titles).

Who it helps: managers and people vetting the bugs other people input (usually to ensure that bugs are entered in a descriptive enough way, aren't already entered from some other perspective, don't refer to an already-closed issue, etc.), and smaller databases for visibility. Labels are nice but this affords a bit more control, optionally.