Closed
Bug 598380
Opened 15 years ago
Closed 14 years ago
Searching within past beta releases is not intuitive
Categories
(Input :: General, defect, P2)
Input
General
Tracking
(Not tracked)
VERIFIED
FIXED
3.0
People
(Reporter: aakashd, Assigned: wenzel)
Details
Steps to Reproduce:
1. Select a previous beta release like Firefox 4 beta 1
2. Enter a search term and press enter.
Actual Results:
Nothing is shown.
Expected Results:
I should see the results of that search term within that beta's set of feedback. The reason its blank is that we're looking at the past 1d,7d,30d by default, but these betas are much older. We should make this smarter and center around the release dates for each set of feedback instead.
| Reporter | ||
Updated•15 years ago
|
Priority: -- → P2
Target Milestone: --- → 3.0
| Reporter | ||
Updated•15 years ago
|
Target Milestone: 3.0 → 2.0
| Reporter | ||
Comment 1•15 years ago
|
||
Per previous conversation, we can set ranges to be:
start-date: release date of selected beta
end-date: release date of the next beta. if it's the latest beta, then no range.
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → fwenzel
| Assignee | ||
Comment 2•15 years ago
|
||
After talking to Dave Dash, a better idea seems to be not to limit by date at all (period: infinite) when searching for a specific beta. The reasoning is that detecting a date resulted in a bagful of development and UX problems:
1) The dates that are chosen come out of thin air and the user does not know where from.
2) After changing the version once, these dates are part of the form, and changing to another beta thereafter will not pick different dates (because you just submitted the first dates with your form).
3) The predetermined date range will discourage you from searching outside that range, even if the data we have on file might not be 100% accurate and there might be interesting things happening 1 or 2 days outside that range.
So I'll give unrestricted (by date) search a shot, to see if this is more intuitive.
| Assignee | ||
Comment 3•15 years ago
|
||
Aaaand due to code and string freeze, I am pushing this to 2.1.
However, I'll have some code ready for review soon.
Target Milestone: 2.0 → 2.1
| Assignee | ||
Comment 4•15 years ago
|
||
Dave Dash: r? https://github.com/fwenzel/reporter/compare/infinity
| Assignee | ||
Updated•15 years ago
|
Status: NEW → ASSIGNED
| Reporter | ||
Updated•15 years ago
|
Target Milestone: 2.1 → 3.0
| Assignee | ||
Comment 5•14 years ago
|
||
Done, including test:
http://github.com/fwenzel/reporter/commit/859ed76
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 6•14 years ago
|
||
QA: You can test this by switching to 4.0b6 or earlier on prod, and compare the results with the same thing on stage.
Updated•14 years ago
|
Flags: in-testsuite?
Flags: in-litmus?
Comment 7•14 years ago
|
||
Verify results display in stage with none found in prod for older beta releases
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Component: Input → General
Product: Webtools → Input
You need to log in
before you can comment on or make changes to this bug.
Description
•