| Summary: | Number of new bug comments in past N days | ||
|---|---|---|---|
| Product: | Community | Reporter: | Bjorn Freeman-Benson <bjorn.freeman-benson> |
| Component: | Dashboard | Assignee: | Diego Figueroa <dfiguero> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dfiguero |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 109221, 129862 | ||
| Bug Blocks: | |||
|
Description
Bjorn Freeman-Benson
Would this measure be the combined number of comments for all bugzilla products of a project? Also should the code take the isprivate field from the comments table into consideration before counting the post? Also how many days back should the code look for? Comments for the last 7 and 30 days? Re comment #2 - yes, 7 and 30. Re comment #1 - yes; ignore isprivate comments. How do I incorporate the number of bug comments into the liveness? Add the number to the CVS download and I'll look at the data and figure out what a good function should be. Patch on bug 134275 applied. Can't tell if this is fixed because the dashboard CSV files are empty. There is a bug with the CSV downloads (which we are trying to fix right now) were if the stats haven't been computed for the day it will not detect the latest date. However, I ran the stats manually and you can see the number of comments and the CSV files. Closed. |