[SUMO KPI dashboard] option for daily and weekly data on questions charts

VERIFIED FIXED in 2012-02-21

Status

support.mozilla.org
General
P1
normal
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: rrosario, Assigned: rrosario)

Tracking

unspecified
2012-02-21

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=sumo-team c=kpidash s=2012.3 p=2)

(Assignee)

Description

6 years ago
Currently, all the KPI charts implemented are graphing monthly data. For some of the charts, we need to be able to show finer detail so that the SUMO team can see the effects of different activities (SUMO days, for example).

The more important ones to have are:
* Questions solved
* Questions with action within 72 hrs

Let's start with these two in this bug. The data for these two graphs is currently calculated with an annotated ORM query on the questions and answers models. These queries are already a little slow for the monthly graphs, so we should do some timings and figure out if we want to continue to use queries, use the kpi.models.Metrics model (like our CTR data) or redis (like our article helpfulness charts already do).
(Assignee)

Comment 1

6 years ago
Adding to 2012.4 sprint for now. I think the SUMO team wants this sooner but we need to trim down the 2012.3 backlog first since it is grown too much already.

This bug is at least a 2pter.
Assignee: nobody → rrosario
Whiteboard: u=sumo-team c=kpidash s=2012.4 p=
(Assignee)

Comment 2

6 years ago
Making this the top KPI dashboard priority for the current 2012.3 sprint and dropping AoA graph to a P2.
Whiteboard: u=sumo-team c=kpidash s=2012.4 p= → u=sumo-team c=kpidash s=2012.3 p=2
(Assignee)

Comment 3

6 years ago
https://github.com/mozilla/kitsune/commit/62e2ecfd966efcc3be14b8e1bba24264bee22252
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: 2012Q1 → 2012-02-14
(Assignee)

Updated

6 years ago
Target Milestone: 2012-02-14 → 2012-02-21
Verified two new Questions graphs display at the top of the KPI dashboard
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.