Component
Frontend UI
Describe the Feature Request
The current default ordering of closed proposed changes is wrong: they are
listed oldest → newest, so the most recently closed items are buried at the
bottom of the list. This is the opposite of what users expect from a history
view, and there is no way to reorder or filter by date from the UI.
Requested, in priority order:
- Fix the default sort — closed proposed changes should default to
newest → oldest so the most recently closed appear first.
- Sort control — let users sort closed proposed changes by date
(ascending / descending).
- Date filter — let users narrow the list to a date range.
At minimum, the wrong default should be corrected. Sort and filter controls
are the fuller solution but can follow.
Describe the Use Case
When reviewing history, the proposed changes people care about most are the
ones that were closed most recently. With the current (incorrect) oldest-first
default, users have to scroll past a long backlog of old, closed items to
reach the recent ones, which gets worse over time as the list grows.
Newest-first ordering makes the recently closed changes immediately reachable.
Additional Information
Scope note: the request is specifically about the closed proposed changes
view. Even if sort/filter controls are out of scope for now, correcting the
default ordering to newest-first would resolve the primary pain point.
Component
Frontend UI
Describe the Feature Request
The current default ordering of closed proposed changes is wrong: they are
listed oldest → newest, so the most recently closed items are buried at the
bottom of the list. This is the opposite of what users expect from a history
view, and there is no way to reorder or filter by date from the UI.
Requested, in priority order:
newest → oldest so the most recently closed appear first.
(ascending / descending).
At minimum, the wrong default should be corrected. Sort and filter controls
are the fuller solution but can follow.
Describe the Use Case
When reviewing history, the proposed changes people care about most are the
ones that were closed most recently. With the current (incorrect) oldest-first
default, users have to scroll past a long backlog of old, closed items to
reach the recent ones, which gets worse over time as the list grows.
Newest-first ordering makes the recently closed changes immediately reachable.
Additional Information
Scope note: the request is specifically about the closed proposed changes
view. Even if sort/filter controls are out of scope for now, correcting the
default ordering to newest-first would resolve the primary pain point.