Closed
Bug 535830
Opened 15 years ago
Closed 7 years ago
Top crash start_date and end_date should reflect data returned
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ozten, Unassigned)
References
Details
per chofmann in #breakpad
The TopCrashersSigRankAPI should populate start_date and end_date based on the data returned, not on the requested window.
Steps
1) Add a new product/version
2) Run cron
3) Go to new top crashers by signature page such as http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.6b5
Expected:
Intro paragraph:
Top 198 Crashing Signatures 2009-12-18 07:00:00 through 2009-12-18 08:00:00.
Actual:
Top 198 Crashing Signatures 2009-12-04 08:00:00 through 2009-12-18 08:00:00.
Comment 1•15 years ago
|
||
Priority?
Comment 2•15 years ago
|
||
lower priority, but seems like it should be a simple fix. I causes a bit of confusion when people start looking at the data just after a new product/version is set up.
Assignee | ||
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
Updated•13 years ago
|
Component: General → Webapp
Comment 3•13 years ago
|
||
Is this still a bug? Going to https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/13.0a1 the line there reads:
"Top 300 Crashing Signatures. 2012-02-02 through 2012-02-09."
Comment 4•13 years ago
|
||
We were talking about this today, and I personally feel like the requested functionality would be more confusing for users.
Maybe we should add a different line with this detail?
Comment 5•11 years ago
|
||
This API call is gone.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 6•11 years ago
|
||
Let's highlight it if the returned data range is different from the requested one and show the actual
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: TopCrashersSigRankAPI start_date and end_date should reflect data returned → Top crash start_date and end_date should reflect data returned
Comment 8•7 years ago
|
||
This API call is gone, and so are the underlying data stores. Let's file a new bug if we still need this feature in the new UI.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•