Store application state changes

Bug #890533 reported by Anthony Lenton on 2011-11-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Developer registration portal
Anthony Lenton

Bug Description

Application state changes should be stored in the DB so that we can extract several metrics about how apps move through the different states. Some of the queries the app state transition log should support are:
 - How many apps were there in state X on day M?
 - How long do apps remain in state X on average (considering the last T days)?
 - How long are apps taking to get from state X to state Y on average (considering the last T days)?

One option would be to store just (timestamp, start_state, end_state, comment), and work everything else out in the app for now.

Changed in developer-portal:
status: New → Confirmed
importance: Undecided → Medium
Anthony Lenton (elachuni) wrote :

The related branch stores just (timestamp, end_state, comment) not start_state as the bug description suggests. More details in the MP.

Changed in developer-portal:
status: Confirmed → In Progress
assignee: nobody → Anthony Lenton (elachuni)
tags: added: kb-feature sp-1
Changed in developer-portal:
status: In Progress → Fix Committed
Changed in developer-portal:
milestone: none → 11.11
Changed in developer-portal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers