Closed Bug 1157655 Opened 10 years ago Closed 9 years ago

waiting times are borked (by ES) in the updates and rereview queues

Categories

(Marketplace Graveyard :: Reviewer Tools, defect, P3)

Avenir
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
2015-05-05

People

(Reporter: eviljeff, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [marketplace-transition])

The waiting time column is broken for the updates and rereview queues. In the updates queue the sort is still correct (by the date of the latest version) but text in the column is from the original nomination, meaning the actual waiting time can't be seen (only the order). In the rereview queue both the sort and the text are incorrect - both are showing time from the nomination instead of time since the app was added to the rereview queue.
toggling off 'reviewer-tools-elasticsearch' reverts to the correct behaviour so its linked to ElasticSearch.
Summary: waiting times are borked in the updates and rereview queues → waiting times are borked (by ES) in the updates and rereview queues
Assignee: nobody → robhudson.mozbugs
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2015-05-05
The re-review queue is returning "Oops! We had an error." message after enabling "reviewer-tools-elasticsearch" on Stage
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I found http://sentry.dmz.phx1.mozilla.com/marketplace-stage/marketplace-stage/group/27611/ It looks like it just needs a reindex, which I started. I reactivated the waffle.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
There is one single page for all apps in re-reviews queue and waiting times are not correctly ordered : http://screencast.com/t/bJXh4lQVZxEA
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Priority: -- → P3
Blocks: 1066368
Assignee: robhudson.mozbugs → nobody
Status: REOPENED → RESOLVED
Closed: 10 years ago9 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in before you can comment on or make changes to this bug.