Closed
Bug 971782
Opened 11 years ago
Closed 10 years ago
Weekly view in support forum metrics dashboard is broken
Categories
(support.mozilla.org :: Knowledge Base Software, task, P3)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2014Q2
People
(Reporter: atopal, Assigned: rrosario)
Details
(Whiteboard: u=sumo-team c=kpidash p=1 s=2014.11)
I was looking at the new product specific charts on the support forum metrics dashboard, and something that caught my eye is that in the daily view for Firefox OS and Android we can see the solution rate at 100% for some days, but switching to weekly shows the solution rate at 0% for the last 6 month. It should probably be closer to a few percent.
Firefox OS showing 0% solved threads in weekly view:
https://support.mozilla.org/en-US/questions/dashboard/metrics/en-US?product=firefox-os
Firefox for Android alternating between 0% and something in weekly views:
https://support.mozilla.org/en-US/questions/dashboard/metrics/en-US?product=mobile
Assignee | ||
Comment 1•11 years ago
|
||
Guessing this is a small and easy to track down js bug -> 1pt
Whiteboard: u=sumo-team c=kpidash p= s=2014.4 → u=sumo-team c=kpidash p=1 s=2014.4
Assignee | ||
Comment 2•11 years ago
|
||
Moving along during sprint planning.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.4 → u=sumo-team c=kpidash p=1 s=2014.5
Assignee | ||
Comment 3•11 years ago
|
||
Moving our P4s to the backlog.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.5 → u=sumo-team c=kpidash p=1 s=2013.backlog
Reporter | ||
Comment 4•11 years ago
|
||
Moving to next sprint per request.
Whiteboard: u=sumo-team c=kpidash p=1 s=2013.backlog → u=sumo-team c=kpidash p=1 s=2014.6
Comment 5•11 years ago
|
||
Looking closely at the data, I think this may be because there are holes in the data. I'll need to pull down a new DB dump to look more closely at it.
Assignee: nobody → mcooper
Assignee | ||
Comment 6•11 years ago
|
||
(In reply to Mike Cooper [:mythmon] from comment #5)
> Looking closely at the data, I think this may be because there are holes in
> the data. I'll need to pull down a new DB dump to look more closely at it.
That's what I was suspecting too. I think this broke when I switched from tastypie to django rest framework. So we either need to make the js lib handle that or we need to zero fill the data in python or js.
Assignee | ||
Comment 7•11 years ago
|
||
This missed the sprint. Moving to next.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.6 → u=sumo-team c=kpidash p=1 s=2014.7
Assignee | ||
Comment 8•11 years ago
|
||
Moving to next sprint during planning.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.7 → u=sumo-team c=kpidash p=1 s=2014.8
Assignee | ||
Comment 10•10 years ago
|
||
Pushing this to next sprint.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.8 → u=sumo-team c=kpidash p=1 s=2014.9
Assignee | ||
Comment 11•10 years ago
|
||
Moving to the next sprint.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.9 → u=sumo-team c=kpidash p=1 s=2014.10
Assignee | ||
Updated•10 years ago
|
Assignee: mcooper → nobody
Assignee | ||
Comment 13•10 years ago
|
||
pushing to next sprint again.
Whiteboard: u=sumo-team c=kpidash p=1 s=2014.10 → u=sumo-team c=kpidash p=1 s=2014.11
Assignee | ||
Comment 15•10 years ago
|
||
In a pull request:
https://github.com/mozilla/kitsune/pull/2003
Assignee | ||
Comment 16•10 years ago
|
||
Assignee | ||
Comment 17•10 years ago
|
||
Deployed to prod now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•