#2 Issue Summary Report

[ngoodman-pentah]

Build a report spec here:
Assignment Summary Report (OK, hard coded pririties
with doc)
Filter: Release Versions, Products, Status (prompt)
Columns: By Assignee, Severity Levels (p1, p2, p3, p4,
etc.)
Drill Link on:
row - By Assignee to Issue Detail (context: assignee,
release version and products)
column - Severity Levels to Issues Detail (context:
severity, release version and products)
data - intersections (context: assignee, severity,
release version and products)
Product as a filter doesn't make any sense since they
can't pass these contexts to the issue detail report
and is confusing for the user. If you're looking at a
10 at the intersection and then clicking get's you MORE
since it's not filtered by product on the detail report.
Drill throughs work, but only kind of. See below note
on “secure filter” issues with default values like “All.”
These are all hard coded priorities; this is not good
overall. The names, the URL generation, the SQL area
all dependent on the list of priorities (data
specific). This doesn't translate to other
environments (every location that wants this report
would have to rewrite for their dictionary of
priorities).

Barely functional version for Pentaho internal data only.

Use the "Guzaldo Method" for buliding varied crosstab
queries and templates:
http://www.pentaho.org/index.php?option=com_content&task=view&id=173&Itemid=276