Closed
Bug 635942
Opened 14 years ago
Closed 14 years ago
Search by submission date does not return any results
Categories
(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
6.0.0
People
(Reporter: krupa.mozbugs, Assigned: kumar)
References
()
Details
Attachments
(2 files)
steps to reproduce:
1. Upload a new add-on and choose full review
2. Load https://addons.allizom.org/z/en-US/editors/queue/nominated
2. In Advanced Search, select submission days to 1 day
expected behavior:
The newly submitted add-on is listed in the search results
actual behavior:
No search results found
Also:
This feature is broken in allizom remora but works fine in prod.
| Assignee | ||
Comment 1•14 years ago
|
||
Jorge, what is the desired behavior for selecting Days Since Submission = 1?
The current code will give you, literally, all addons submitted a day ago. It sounds like Krupa is expecting it to give you addons submitted anytime *between* now and a day ago. In other words, for it to show all addons submitted today and yesterday. I'm not sure what remora does; I can change it to whatever works best.
Note that this is different than Days Since Submission = 2 or 3, etc. Those queries will show you addons submitted 2 days ago, 3 days ago, ....
Comment 2•14 years ago
|
||
I think it's more useful to show add-ons that have were submitted in X days or less. The ones that have been submitted exactly X days ago will appear at the top anyway, so it is effective regardless of interpretation.
Updated•14 years ago
|
Priority: -- → P3
Target Milestone: 5.12.12 → 6.0.0
| Assignee | ||
Comment 3•14 years ago
|
||
ok, I made it work like Jorge describes: https://github.com/jbalogh/zamboni/commit/795d951211393ed819bc0be6286fd547ea874672
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•14 years ago
|
||
Status: RESOLVED → VERIFIED
| Reporter | ||
Comment 5•14 years ago
|
||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•