266062 - Reorganize reports.cgi homepage to display preset reports

Status: NEW

(Bugzilla :: Reporting/Charting, defect)

Description

[Christian Reis]

We have pretty awesome reporting facilities, but it is currently quite difficult
to realize they exist, and it's a chore to produce some common queries that
could be preset for us.

For instance, getting bug counts per engineer is a common task, but nowhere do
we hint to the Bugzilla user that it is easily obtained from our reporting
facilities. Additionally, too often have I tried charting and graphing but just
obtained broken output and gave up without realizing I was just not fiddling
with the right knobs.

My suggestion is to reorganize reports.cgi to include a set of links that
represent common end-user tasks, allowing one-click access to them. This has the
advantage of serving as an introduction to our reporting facilities that can
invite him to gradually experiment and tinker with the options ready.

Comment 1

[Gervase Markham [:gerv]]

kiko and others: I've been having a think about this. What sort of preset
reports would you suggest? 

Suitable candidates:

- Can't use optional features (e.g. QA, UNCO)
- Can't be a big performance hit on any installation (e.g. a list of all accounts)
- Should use vertical, vertical and horizontal, and all three dimensions
- Should demonstrate query area refinement

Suggestions welcomed.

Gerv

Comment 2

[Dave Miller [:justdave]]

How about all the canned reports that were on the "Bugzilla Query Kitchen" page
that are supposedly going away because they can be done in the new system?  We
should make them as easy to get at on the new system as they were on the old.

Comment 3

[Christian Reis]

Report requests that commonly come up to me:

  - Bugs assigned per engineer per status (like the doomed reports)
  - Open bugs assigned per engineer per priority and severity

Time-based reports:

  - Bug counts per status per day of a week
  - Bug counts per status per week 
  - Bug status count profiles over time

Comment 4

[Gervase Markham [:gerv]]

The problem with Query Kitchen reports like "Most Doomed" (or anything else
per-engineer) is that if you ran the same report, you'd get a 100,000 row table
with every Bugzilla account in it. Having people click on that "to see what it
does" could be a perf problem.

(You could argue that this is a limitation of charting which needs to be fixed;
nevertheless, it's currently true.)

Kiko: I'm not sure reporting can do any of the "time-based reports" you list.

Gerv

Comment 5

[Gervase Markham [:gerv]]

BTW, I've just noticed that fixing the 100,000 person problem is bug 271673.

Gerv