866760 - Record stats for app review times

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Statistics, defect, P4)

Description

[Andrew Williamson [:eviljeff]]

We'd like to record the time spent in the queue for a completed app review, e.g. time from the nomination date to the date when the app is either approved or rejected.

And then get access to that data somehow (however the rest of the stats access is implemented/planned)

Comment 1

[Rob Hudson [:robhudson]]

Would this result in a chart ultimately? E.g. somewhere in the reviewer tools, like a dashboard? Or accessed in some other way?

Is time spent in queue in "days" granular enough?

Would we track time spent in the queue per date when it was reviewed? E.g. if you did 3 reviews on 4/29/13, there would be 3 values of [5d, 3d, 8d].

For either the chart or whatever else, would you expect an average back? So in the above example, you'd get a value of {"date": "2013-04-29", "value": "5.3"}.

Do you want extra dimensions along with this data to be tracked, like hosted vs packaged, which queue it was in, etc?

Comment 2

[Andrew Williamson [:eviljeff]]

(In reply to Rob Hudson [:robhudson] from comment #1)
> Would this result in a chart ultimately? E.g. somewhere in the reviewer
> tools, like a dashboard? Or accessed in some other way?

Ideally it would be added to the existing statistics dashboard at: https://marketplace.firefox.com/statistics/
though I'm not sure that its flexible enough for this data

> Is time spent in queue in "days" granular enough?

yes, I think so.

> Would we track time spent in the queue per date when it was reviewed? E.g.
> if you did 3 reviews on 4/29/13, there would be 3 values of [5d, 3d, 8d].
>
> For either the chart or whatever else, would you expect an average back? So
> in the above example, you'd get a value of {"date": "2013-04-29", "value":
> "5.3"}.

it would depend on what kind of average was being requested.  If it was a daily average, then yes.  Probably used more frequently would be a weekly and monthly average (so the average off all review times in that week period - note: not the average of the daily averages)
 
> Do you want extra dimensions along with this data to be tracked, like hosted
> vs packaged, which queue it was in, etc?

hmm...  that would be good!  
* Hosted; Packaged:web; Packaged:privileged
* Submission; Update (I'm not sure the other queues make sense - re-reviews aren't visible to the developer; and anything in the escalation queue should be counted as what it is - i.e. a submission, an update, etc)