Standard reports

[Christian Robottom Reis]

On Fri, Nov 19, 2004 at 02:40:17PM -0800, Stuart Donaldson wrote:
> I then created a pre-defined reports page which allows selecting a 
> product, and a report for which it then will generate the report. It 
> uses a small modification  to buglist.cgi in order to load the query 
> based on the product selected and report selected, much like buglist.cgi 
> can load a named query.

It's an interesting approach; I thought of something different, which
I'll explain here. I have a long-term idea that we should have more
"domain-specific" pages in Bugzilla: a page for viewing a User, a page
for viewing a Product, a page for viewing a Group. These pages' main
goal would be to provide general information on the entity, with links
to ready-made reports and interesting statistics (for a Product,
answering the questions how many open bugs? how many all-time closed
bugs? can I see a full report of them?) and other entity-related tasks
(file a bug on this product, edit this product -- for admins).

This is a framework that I think would "bring out" a lot of the richness
that is hidden in Bugzilla, giving these entities homes instead of being
cut apart in half a dozen different pages. Bugzilla is very much
divided into tasks, and I would like to see it more divided into
concepts and then offering tasks upon those concepts. I think this
provides a better interaction model.

Bringing us back into the concrete world, by this I mean that I would
prefer seeing a page with links to ready-made reports kept as a template
(so it is rather easily customizable and reduces the requirement of Yet
Another Administrative Interface for these reports) in something like
show_product.cgi. 

Too blue-skyish?

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331