Bug 425447

Summary: Discover should offer the option to show newest reviews first
Product: [Applications] Discover Reporter: Guo Yunhe <i>
Component: discoverAssignee: Dan Leinir Turthra Jensen <leinir>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: aleixpol, bugseforuns, nate
Priority: NOR Keywords: usability
Version First Reported In: 5.19.4   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Krita reviews

Description Guo Yunhe 2020-08-17 08:24:25 UTC
SUMMARY


STEPS TO REPRODUCE
1. Open Discover
2. Open Krita page
3. Check the reviews section

OBSERVED RESULT
The oldest reviews were shown first

EXPECTED RESULT
The newest reviews should be be shown first

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20200815
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.0-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa DRI Intel® UHD Graphics 620

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-08-18 22:07:48 UTC
It doesn't show the oldest reviews first, it shows the most highly rated reviews first, which I think is sensible. However a side effect is that older reviews have had more time to accumulate ratings, so I can see why you would think that it sorts oldest first.

I suppose it could offer you the choice of sorting the reviews by newness vs quality.
Comment 2 Guo Yunhe 2020-08-19 06:35:46 UTC
Created attachment 130991 [details]
Krita reviews

From what I see, here is a 4 star review before other 5 star reviews. So it mustn't be ordered by rating stars...
Comment 3 Nate Graham 2020-08-19 14:55:28 UTC
Reviews aren't sorting by the review's rating, but by other people rating the review itself!:) The screenshot shows that the top review is yours, which has 3/3 "useful" votes.

I don't know how it decides to sort other reviews when all of them have the same usefulness count though.
Comment 4 Nate Graham 2023-01-12 18:52:58 UTC

*** This bug has been marked as a duplicate of bug 462652 ***