678168 - Show different time frames on the dashboards

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Software, task, P2)

Description

[Kadir Topal [:atopal]]

Currently we show "this week" and "overall", but there is too much volatility in "this week" and too little in "overall" (+ no one knows what time span overall covers)

Instead we should have 3 views: last 7 days, last 30 days, last 3 month
and the standard view should be 30 days.

Comment 1

[Verdi [:verdi] Best to slack me]

Yes please! This will be much better for us.

Comment 2

[James Socol [:jsocol, :james]]

Erik: do we even have that data from webtrends? I thought the week/overall was because that's what their API gave us.

Comment 3

[[:Cww]]

We specify the date range we want so we can ask for whatever we want. I can work with Erik on getting the webtrends queries.

Comment 4

[[:Cww]]

One thing to note is how often do we expect that data to update.  Are we doing a webtrends pull every day for "past 7, past 30, past 90" or are we pulling once a week for past 7, once a month for past 30 etc.  The latter is much friendlier to webtrends but it's a little confusing.

Comment 5

[Kadir Topal [:atopal]]

It should be every day. So we have a rolling period of last 7 days/30days/90days. otherwise it would really be confusing and also not of much use. It's much more useful to know the top 20 for the last 30 days than that of the last full month.

Comment 6

[Erik Rose [:erik][:erikrose]]

Yep, we pull every day for every period. This shouldn't be a big deal, except that we should revise the UI.

Comment 7

[Kadir Topal [:atopal]]

I guess it would be okay to go with the current UI, since we would only add one additional state. But I agree, in the future that UI should be revised.

Comment 8

[Scoobidiver (away)]

Can we have a new target milestone?

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

Cleaning up 2011Q4

Comment 10

[Ricky Rosario [:rrosario, :r1cky]]

Quite a bit to do here. Figure out API calls, store the data, update the UI,...

Making it a 3pter, but we may want to spin off new bugs once we take a closer look.

Comment 11

[Ricky Rosario [:rrosario, :r1cky]]

Pruning 2012.5 bug list.

Comment 12

[Ricky Rosario [:rrosario, :r1cky]]

Sprint based milestone :-)

Comment 13

[Ricky Rosario [:rrosario, :r1cky]]

Revising points based on what I have learned working on l10n coverage metric.

Comment 14

[Ricky Rosario [:rrosario, :r1cky]]

Actually, I need to have this for the l10n coverage calculation (Bug 727084). Moving this to the current sprint.

Comment 15

[Ricky Rosario [:rrosario, :r1cky]]

Actually, this is pretty easy the way Erik set it up => 1pt

Comment 16

[Ricky Rosario [:rrosario, :r1cky]]

Landed on prod:

https://github.com/mozilla/kitsune/commit/0fe179b25e6b1dead2c4e1eaf86088db950a3aae

Data for the new time frames will be missing until the daily cron job runs.