github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Sort milestone drop-down list on issues page #2360

New Issue
Closed
opened 2025-11-02 04:33:49 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 04:33:49 -06:00
Owner
Copy Link

Originally created by @bugreport0 on GitHub (Sep 27, 2018).

  • Gitea version (or commit ref): 1.5.1

Description

Milestones are sorted almost everywhere, but not in the drop-down filter box on the issues page.

To reproduce

  1. Create a 'v2.0' milestone (assign a date like 2019-02-02)
  2. Create a 'v1.0' milestone (assign a date like 2019-01-01)
  3. Observe that milestones are sorted in the milestone overview and the 'set milestone for issue' list
  4. Observe that milestones are not sorted in the 'milestone' drop-down filter on the issues page
Originally created by @bugreport0 on GitHub (Sep 27, 2018). - Gitea version (or commit ref): 1.5.1 ## Description Milestones are sorted almost everywhere, but not in the drop-down filter box on the issues page. ## To reproduce 1. Create a 'v2.0' milestone (assign a date like 2019-02-02) 2. Create a 'v1.0' milestone (assign a date like 2019-01-01) 3. Observe that milestones are sorted in the milestone overview and the 'set milestone for issue' list 4. Observe that milestones are **not** sorted in the 'milestone' drop-down filter on the issues page
GiteaMirror added the type/enhancement label 2025-11-02 04:33:49 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2360
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?