Closed abhn closed 1 month ago
@abhn Does #15077 implement your use cases?
Yep, both this new column (created datetime of an add-on) and the existing last-updated column should be sortable.
this will cover the use-case of seeing add-ons arranged in a predictable and stable order.
In case of multi-page content review queue (which doesn't happen often, but still), we'd like the whole queue to be sorted by sort-column actions (and not just add-ons in the current view), (ideally) with a unique URL for each queue sort order to be able to bookmark, and refresh after processing entries.
In case of multi-page content review queue (which doesn't happen often, but still), we'd like the whole queue to be sorted by sort-column actions (and not just add-ons in the current view), (ideally) with a unique URL for each queue sort order to be able to bookmark, and refresh after processing entries.
To my understanding, that is the default behavior, at least it's what is happening for the other queues as well. Feel free to add a comment to other ticket if it's of concern.
Closing as duplicate of #15077.
Description
As a add-ons content reviewer, I'd like the content review queue to behave more like a queue (items sorted in ascending order of the timestamp they entered the queue) so that we can avoid a random-ish order of items in the queue and get to items in a consistent-timely manner.
Note about the WIP
We couldn't think of one best way to best arrange the content review queue but have some ideas.
(I'm creating this ticket to put down the thoughts we already have to start a discussion on how to improve the queue ordering. The requirement definition is still very much missing)
Acceptance Criteria
Checks
┆Issue is synchronized with this Jira Task