Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sorting by Recently updated/Least recently updated not working #1938

Closed
2 of 7 tasks
ghost opened this issue Jun 11, 2017 · 1 comment · Fixed by #2204
Closed
2 of 7 tasks

Sorting by Recently updated/Least recently updated not working #1938

ghost opened this issue Jun 11, 2017 · 1 comment · Fixed by #2204
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself

Comments

@ghost
Copy link

ghost commented Jun 11, 2017

  • Gitea version (or commit ref): 1.1.1
  • Git version: Not sure (3rd party service - Teknik.io)
  • Operating system: Windows Server 2016 Datacenter
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No but I can at Teknik.io
    • Not relevant
  • Log gist: N/A

Description

Sorting by Recently updated/Least recently updated, seems to have no effect.
In the test link above, the post Keep 3rd party services up to date or Suggestions for future services have been updated 1 day ago.

GitHub shows updated 3 hours ago next to opened 7 months ago by someuser when sorting by last update, so I wonder if this is actually implemented in Gitea.

Screenshots

screencap-1497187960331

@bkcsoft bkcsoft added issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself backport/v1.1 labels Jun 15, 2017
@bkcsoft
Copy link
Member

bkcsoft commented Jun 15, 2017

Since this is most likely a regression I'm adding the backport-label

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant