Add fields needed in ES for reviewer tools queues

RESOLVED FIXED

Status

P4
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: robhudson, Assigned: robhudson)

Tracking

Avenir
x86
Mac OS X
Points:
---
Dependency tree / graph

Details

(Whiteboard: [qa-])

(Assignee)

Description

4 years ago
Come up with fields needed to move reviewer tools to elasticsearch and add them to the index and indexing code.
(Assignee)

Updated

4 years ago
Blocks: 1066372
(Assignee)

Updated

4 years ago
Blocks: 1066373

Updated

4 years ago
Priority: -- → P4
(Assignee)

Updated

4 years ago
Assignee: nobody → robhudson.mozbugs
(Assignee)

Comment 1

4 years ago
The following fields will need to be added. I'm using the proposed paths in the ES document for naming here:

* priority_review (used for app_flags)
* num_abuse_reports (displayed in the queue)
  - I'm curious how important this is to stay current (index when it changes) vs doing a db query for this or even if it's an important column in the queue.
* is_rereviewed (like is_escalated, will be used for re-review queue)
* latest_version.nomination_date (for sorting)
* latest_version.created_date (for sorting, fallback if nomination doesn't exist)

I haven't looked into the special queues (tarako, China queue) or the moderated reviews.
(Assignee)

Updated

4 years ago
Summary: Investigate fields needed in ES for reviewer tools queues → Add fields needed in ES for reviewer tools queues
(Assignee)

Comment 2

4 years ago
https://github.com/mozilla/zamboni/commit/186a110 

I'll close. When implementing the other queues if any field is missing we can add it along with those bugs.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.