Open
Bug 244633
Opened 20 years ago
Updated 12 years ago
Need derivative graphs
Categories
(Bugzilla :: Reporting/Charting, enhancement)
Bugzilla
Reporting/Charting
Tracking
()
NEW
People
(Reporter: eyalroz1, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a1) Gecko/20040520 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a1) Gecko/20040520 The graph creation system must offer the option of showing the derivatives (and/or smoothed derivatives) of numbers-of-bugs over time, i.e. to show, for each point in time, how many bugs (of the type charted) were added per unit of time. smoothing the derivate will mean taking plus-and-minus X/2 days from the point in time plotted, counting the total number of bugs of relevant type added in that time frame, and dividing by X. Reproducible: Always Steps to Reproduce:
Comment 1•20 years ago
|
||
Have you already tried to accomplish this by using the "changedfrom" or "changedto" options in the boolean charts?
Reporter | ||
Comment 2•20 years ago
|
||
I'm not sure I understand what you mean. To clarify: Limiting the range of the graph is not what I'm asking for. I want to be able to see, over a large period of time, a graph of the rate of bug additions. Specifically, I don't see "changedfrom" or "changedto" fields in the URLs generated for me. An example: http://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=400&label0=All+Open&line0=400&label1=VERIFIED&line1=390&label2=All+Open&line2=400&cumulate=1&datefrom=2000-01-01&dateto=2004-05-23&action-wrap=Chart+This+List Only "datefrom" and "dateto" are reminiscent of them.
Comment 3•20 years ago
|
||
You should be able to specify that the series should include bugs selected by a criteria that, for example, STATUS changedto RESOLVED and STATUS changedafter 2d and get the count of bugs that became resolved in the last 48 hours. However, that does not seem to be working properly in the boolean search charts.
Comment 4•20 years ago
|
||
That'd probably be bug 179671. I can get this to work without boolean charts though... in the top part of the form, in the Bug Changes section... Only bugs changed between: [ 2d ] and [ Now ] (YYYY-MM-DD or relative dates) where one or more of the following changed: [ Status ] and the new value was: [ RESOLVED ]
Reporter | ||
Comment 5•20 years ago
|
||
(In reply to comment #3) > You should be able to specify that the series should include bugs selected by a > criteria that, for example, STATUS changedto RESOLVED and STATUS changedafter 2d > and get the count of bugs that became resolved in the last 48 hours. However, > that does not seem to be working properly in the boolean search charts. I'm sure I have no idea what you mean. I tried the chart creation at bugzilla.mozilla.org and at landfill.bugzilla.org/bugzilla-2.17.7 and saw no such option, either working or not-working.
Updated•19 years ago
|
Summary: [RFE] need derivative graphs → Need derivative graphs
Updated•19 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Reporter | ||
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•18 years ago
|
Target Milestone: --- → Bugzilla 3.2
Comment 6•17 years ago
|
||
I will *try* to implement it.
Comment 7•16 years ago
|
||
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
Updated•16 years ago
|
Assignee: gerv → charting
Comment 8•12 years ago
|
||
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved. I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•