Bug 462652 - Option to switch order of reviews between "most helpful" and "most recent"
Summary: Option to switch order of reviews between "most helpful" and "most recent"
Status: CONFIRMED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.26.4
Platform: Neon Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 425447 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-12-04 23:52 UTC by radimir.cacic09
Modified: 2023-01-12 18:54 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Psensor in Discover (257.56 KB, image/png)
2022-12-04 23:52 UTC, radimir.cacic09 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description radimir.cacic09 2022-12-04 23:52:55 UTC 
Created attachment 154320 [details]
Psensor in Discover

SUMMARY

Software reviews in Discover should always be sorted by recent to oldest.
However, this is not always the case.

Sometimes, reviews are sorted by recent to oldest and the other time it's sorted by oldest to recent (it isn't really useful to see reviews from 5 years ago first).

STEPS TO REPRODUCE
1. Open Psensor in Discover (see reviews sorted by oldest to recent)
2. Open PulseAudio Volume Control (see reviews sorted by recent to oldest)
3. Open Muon Package Manager (see reviews sorted by oldest to recent)

OBSERVED RESULT

Sorting seems to be random for different items?

EXPECTED RESULT

I'd expect reviews to always be sorted by recent to oldest. (by default)

Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Graphics Platform: X11
Comment 1 Nate Graham 2022-12-05 19:50:18 UTC 
Yeah it's not really clear what the sort order is right now.

Probably we should default to sorting by "most helpful" and offer an option to switch to "most recent", or the reverse.
Comment 2 Nate Graham 2023-01-12 18:52:58 UTC 
*** Bug 425447 has been marked as a duplicate of this bug. ***