One of the metrics we want for Project metrics for drupal.org redesign is a count of the number of issue reporters for a project in a given week -- the # of unique users filing new issues in that project's queue. Although it can be a little confusing with issues being moved into another queue, I think it's fine to just go with the stats on the original issues.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 889916-3-pi-new-issues-comments-metric.patch | 4.51 KB | hunmonk |
| #3 | pi-new-issues-comments-metric-2.patch | 4.25 KB | hunmonk |
| #2 | pi-reporters-participants-metric.patch | 4.54 KB | hunmonk |
Comments
Comment #1
hunmonk commentedthis metric should merge in the functionality of #889918: Add a function to count the number of issue reports/participants in a week into one multi-value metric, so i closed that issue.
Comment #2
hunmonk commentedattached is *mostly* working. one weird thing is that the count of participants always seems to be either equal to or one higher than the number of reporters, so something is wrong there.
tossing up now for a sanity check on basic approach.
Comment #3
hunmonk commentedfixed a bum query that was causing the count bug reported in #2 -- as far as i can tell, this is now working correctly.
Comment #4
hunmonk commentedlatest patch, adds batch support.
Comment #5
hunmonk commentedcommitted in merge http://drupalcode.org/project/project_issue.git/commit/18ca2d6