product/version filter on the sites page is confusing

VERIFIED FIXED in 2.0

Status

Input
General
--
enhancement
VERIFIED FIXED
7 years ago
7 years ago

People

(Reporter: vish_moz, Assigned: michaelk)

Tracking

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Created attachment 488985 [details]
filter on sites

STR:
1. go to the sites page, http://input.stage.mozilla.com/en-US/sites
2. look at the Product filter on the left

Actual result:
default values on the filter:
'Product' : Firefox , 7d

Suggestions:
The '7d' which actually means last seven days is confusing to users. Product should have a 'versions' filter next to it or we should move the 'When:7d' filter below the product filter like we have it on this page, http://input.stage.mozilla.com/en-US/search/?q=version&product=firefox&version=4.0b6
Michael, is this even supposed to look that way (i.e. 7d as a version alongside 4.0b6 and friends)?
Assignee: nobody → michael
The decision was based off of comments here: https://bugzilla.mozilla.org/show_bug.cgi?id=601639#c3
(Assignee)

Comment 3

7 years ago
Fred, it is done this way deliberately, the reason outlined in bug 601639.

I do not particularly like the way I did it. For once because 7d is not a version (though there is no visible label saying version), but primarily because it is inconsistent to the frontpage.

Neither do I really like the way we do it on the frontpage, where it is easy to poorly combine the fields "when" and version, especially as it is not obvious how to get a matching date range for an older beta. For pre-clustered data, the version-based choices and the date-based choices are mutually exclusive (otherwise we have a total cluster explosion). So having separate controls does make even less sense.

However, I understand that for the sake of consistency it is desirable to closely match the frontpage (while not fully possible, e.g. custom date ranges will not work for the precomputed clusters).

I will not be able to change this before 2.0. I can remove the 7d option though, if usability is paramount in this matter.
Let's remove 7D for now
(Assignee)

Comment 5

7 years ago
Removed. Let’s think that through a bit more for next version.

https://github.com/fwenzel/reporter/commit/ce28d652831670f80a60b73c0a7960883e9cf2f0
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0
(Reporter)

Comment 6

7 years ago
Verified, FIXED.
Status: RESOLVED → VERIFIED
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.