Looks like a good start, but I'd like to see such information accessible on a per-user basis. It'd be nice to just have the wiki auto-embed or auto-link to the generated status report per-user every week. The less w have to do for status reports, the better :)
Initial stab at reports
Review Request #151 — Created Sept. 6, 2007 and submitted
|Review Board SVN (deprecated)|
There's a lot unfinished here, but it's good enough for my purposes ;) The report selector, in particular, needs a lot of love. At the moment it only allows selecting the report and a format. The user and period fields are wired up, but there's no UI.
Out of curiosity, any reason why we don't rearrange reports to be a dictionary with 'report_review_requests', 'report_reviews', and 'report_status_report' keys? I suppose it's for the template, though that should be able to work still and auto-sort alphabetically unless we want to preserve a specific sort order. Anyhow, food for thought. On a similar note, it might be nice to use dictionaries instead of tuples for things like the template name and format and such, to improve code readability in the report function.