Closed
Bug 204363
Opened 21 years ago
Closed 21 years ago
bug inflow and outflow
Categories
(Bugzilla :: Reporting/Charting, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: marius.andreiana, Assigned: gerv)
References
Details
Attachments
(1 file)
13.74 KB,
image/gif
|
Details |
needed for forecasting a product release. Defect inflow is the rate at which new bugs are reported against the system Defect outflow represents the number of bugs fixed each week It is best to graph defect inflow and outflow on a weekly basis; daily graphing has too much variability. I'll attach a sample chart.
Reporter | ||
Comment 1•21 years ago
|
||
Reporter | ||
Comment 2•21 years ago
|
||
The bugs should also have a 'weight' depending on severity, for example: blocker 30 critical 20 major 10 normal 7 trivial 3 enhancement 0
Comment 3•21 years ago
|
||
I'm pretty sure that gerv's stuff can be set up to do the graphing. Not the weight thing, though. Taht woudl also cause issues - what if a bug is reported as critical, then downgraded to normal and fixed the next week. You'd show a net positive result, but thats not what really has happened.
Depends on: 16009
Assignee | ||
Comment 4•21 years ago
|
||
Yes, bug 16009 can graph anything that can be queried - and you can certainly do a query for all bugs filed in the last week etc. But it can't do the weighting thing; you may just want to have a separate query for each weight and then have a sum of them on the chart as well as the individual lines. Gerv
Assignee | ||
Comment 5•21 years ago
|
||
Mostly fixed by bug 16009. Gerv
Status: NEW → 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
•