default organization repository sort order

[agaida]

• Gitea version (or commit ref): current
• all the other things are not relevant for this feature request

Description

Hi, there was several good bug reports about repository sort order but unfortuately all fall short.
Default sorting order should be configurable - best example is a 'morgue' or 'basement' organization - nobody will care when the last commit was done on dead projects - the natural order here would be maybe alphabetic or rev. alpha. So it would be nice if one would be able to set this per org.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[mb2g17]

I second this: sometimes I do commits on old projects to tweak readmes, but I don't want them surfacing to the top of my repositories page. Setting a default sort would be really helpful for this.

For example, the default could remain Recently updated, but there exists some app.ini config property / user property / org property to change it to some other values, like Newest.

[ddetton]

Default sort order should be implemented for everything. Most important would be orgs and repos. I don't care what the default is, as long as there is a way to override it.

[CrysK]

I'm also looking for a way to default sort, especially for the issue tracker (recently updated first).
Is there a way to set a default meanwhile?

[micka190]

Also interested in sorting issues by recently updated first. It's a drag to have to go through multiple issues (sometimes multiple pages) to find the ones that are actively being worked on/discussed.

Edit: For clarity, this is referring to the issues in individual repositories. Gitea's "Issues" page itself seems to already sort by recently updated.

[bobmagicii]

yeah i really wish it would default to sorting by alpha on all our orgs, we aren't treating dev as a race and people just need to be able to find things they need in a consistent way that the alphabet provides. such that, my team uses a tampermonkey script to redirect to ?sort=alphabetically if we visit without a sort set.

in my mind, i feel like the front end should remember that in local storage or something. then like the tampermonkey, its per user choice where they left it.

[TimoNotonica]

Same for me. Define default sort order in app.ini and/or ui.

[levicki]

I am curious, is there any valid reason why configurable sort order hasn't been implemented for 5 years? I get that it's a cosmetic issue compared to making sure other more important features work but still... it's unfathomable that it hasn't been done yet when it's such a basic feature of any list in any GUI.

[lunny]

Should this be a per org level configuration or a system level configuration?

[micka190]

Personally, I'd be happy with a feature that was at least repo level or user level. I don't think system level makes sense since you probably want some flexibility (if there's different sorting modes). I'd prefer repo level over org-level, though I'd settle for org-level if it's the only choice.