[Task]: Expand the review queue filters to all possible reasons an add-on can be enqueued

mozilla / addons

☂ Umbrella repository for Mozilla Addons ✨

Other

127 stars 41 forks source link

[Task]: Expand the review queue filters to all possible reasons an add-on can be enqueued #15148

Open wagnerand opened 2 weeks ago

wagnerand commented 2 weeks ago

Description

As a reviewer or operations person, I want to filter on reasons why an add-on was added to the queue so I can prioritize certain reasons when needed.

Acceptance Criteria

  ### Milestones/checkpoints
  - [ ] The filter list at the top of the queue includes all possible reasons why an add-on can be added to the queue.

Checks

[X] If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task

diox commented 3 days ago

https://github.com/mozilla/addons/issues/15072 will add a couple of those reasons, but there are more that are grouped together currently.

Essentially this is about expanding needs_human_review_other in Version.get_due_date_reason_q_objects() to each individual possible NHR, and adding a description for each at the end of VIEW_QUEUE_FLAGS in olympia/reviewers/models.py. Bonus point for finding a way to keep everything in sync.