Closed
Bug 192893
Opened 22 years ago
Closed 21 years ago
[RFE] ability to specify time window for '# of bugs over time' charts to improve time resolution
Categories
(Bugzilla :: Reporting/Charting, enhancement)
Bugzilla
Reporting/Charting
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: c.hamacher, Assigned: gerv)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b) Gecko/20030202 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b) Gecko/20030202 For the summary graphs over time, the x axis always starts in 1999, with a constant width of the resulting graph. Over time, this leads to increasingly poor time resolution of the resulting graphs. It might be beneficial to add the ability to specify a time window at http://bugzilla.mozilla.org/reports.cgi . Potentially, even a corresponding window for the y-Axis (bug #s) might be useful. This ability would make it easier to look at trends in the bug statistics (e.g. changes after release dates, etc.). Reproducible: Always Steps to Reproduce: 1. go to http://bugzilla.mozilla.org/reports.cgi Actual Results: There is now possibility to enter a time frame Expected Results: Time frame might be useful - potentially a y-Axis window as well
Assignee | ||
Comment 1•22 years ago
|
||
The new charting module, up for review over in bug 16009, has this feature. Gerv
Reporter | ||
Comment 2•22 years ago
|
||
Oh boy - and I thought I did a thorough search before filing this ... OK, since this is already covered in bug 16009: what should I resolve this as? DUPLICATE, INVALID, WFM ... they all don't quite seem to fit. Chris
Assignee | ||
Comment 3•22 years ago
|
||
This seems the best thing to do. I'll resolve this bug as FIXED when 16009 gets checked in. Gerv
Depends on: 16009
Assignee | ||
Comment 4•21 years ago
|
||
Fixed by bug 16009. Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Target Milestone: --- → Bugzilla 2.18
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•