Jazz Reporting Service ready-to-use and ready-to-copy reports

The Report Builder component of Jazz™ Reporting Service includes a number of predefined reports that you can use to analyze the data from across your lifecycle projects.

The predefined reports, which can be imported when Report Builder is installed and configured, are available on the All Reports page. They are organized into the following groups and listed here:

Ready-to-use: Use these reports as they are; you cannot customize them.
Ready-to-copy: Copy these reports and customize them to suit your needs.

Tip: You can also download a collection of Lifecycle Query Engine (LQE) ready-to-copy reports from this Jazz.net wiki page.

Ready-to-use reports

While you cannot modify the ready-to-use reports or use them as templates for creating your own, you can use them to explore your lifecycle data and generate basic reports.

Table 1. Ready-to-use reports that are available in Report Builder
Name	Description
Average cycle time	Shows the trend of the average time that work items stayed in the active state (from activation to being resolved).
Average lead time	Shows the trend of the average time that work items stayed in the unresolved state (from creation to being resolved).
Average time in state	Shows the average time that work items stayed in a particular state.
Blocking work items	Shows a list of open work items that are blocking another work item or test execution record.
Build duration and success	Shows the duration and success of each build of one build definition in the last seven days.
Burndown by hours	Shows the number of estimated hours required to complete work items that are either open or in progress over daily intervals.
Burndown by story points	Shows the number of story points that are assigned to work items that are either open or in progress over daily intervals.
Burndown by work item count	Shows the number of work items that are either open or in progress over daily intervals.
Burnup by hours	Shows the number of hours of completed work over daily intervals.
Burnup by story points	Shows the number of story points that are associated with completed work over daily intervals.
Burnup by work item count	Shows the number of completed work items over daily intervals.
Change set activity	Shows the total number of change sets per day for the last seven days for one or more streams.
Changes to time spent	Shows a list of work items where the time spent was updated within the last seven days.
Cycle time as percentage of lead time	Shows the trend of the cycle time as a percentage of lead time for work items.
Defects by priority chart	Shows the total number of defects by priority for each selected team in the current iteration.
Defects by priority list	Shows the list of work items and their priority, filed against the selected team in the current iteration.
Defects per requirement chart	Shows the number of open versus closed defects that were found during testing grouped by requirement. Only requirements with linked defects that use the affected-by relationships are considered here.
Defects per requirement list	Shows the number of open, closed, and total number of defects that were found during testing grouped by requirements. Only requirements with linked defects that use the affected-by relationship are considered here.
Defects per test case chart	Shows a bar chart for each test case with the number of open versus closed defects that were found during testing. Filter by one or more test plans, which are listed by their project areas in the filter property.
Defects per test case list	Shows the open, closed, and total number of defects that were found during testing by their test case. Select one or more test plans to consider for this report.
Incomplete stories	Shows the stories that are targeted to the current iteration that have not been completed.
Iteration health	Shows various statistics that can be used to interpret the health of the current iterations filtered by timelines. Only currently ongoing iterations are shown; you can identify them by looking at the start and end dates.
Process control - cycle time	Shows the time that a work item stayed in the active state.
Process control - lead time	Shows the time that a work item stayed in the unresolved state.
Release burndown by hours	Shows the amount of work outstanding for an iteration, in hours, broken down by its direct child iterations.
Release burndown by story points	Shows the amount of work outstanding for an iteration, in story points, broken down by its direct child iterations.
Release burndown by work item count	Shows the number of outstanding work items for an iteration, broken down by its direct child iterations.
Release burnup by hours	Shows the amount of work completed for an iteration, in hours, broken down by its direct child iterations.
Release burnup by story points	Shows the amount of work completed for an iteration, in story points, broken down by its direct child iterations.
Release burnup by work item count	Shows the number of completed work items for an iteration, broken down by its direct child iterations.
Release status chart	Shows a chart of the number of open and closed stories for a release.
Release status list	Shows a list of the remaining open stories for a release.
Scope added	Shows work items that were added to the current iteration scope after the iteration's start date.
Scope removed	Shows work items that were removed from the current iteration scope after the iteration began.
Story traceability	Shows a table of open user stories with traces to requirements and test cases, as well as the number of open defects that are found during testing. To filter the list, select a single team area and optionally an iteration name.
Team dependencies	Shows a list of open work items that are blocked by other teams' open work items. The list is sorted by the blocking team's name and work item severity. To filter the list of blocked items, select one or more team areas.
Team velocity	Shows the number of story points that are completed in each iteration.
Test cases per requirement	Shows the total number of test cases per requirement. Only requirements with associated test cases are shown.
Test execution per requirement	Shows a chart of the number of test cases by execution status per requirement.

Ready-to-copy reports

You can use the ready-to-copy reports as a basis for creating your own. Simply duplicate the report and customize it to suit your needs.

Table 2. Ready-to-copy reports that are available in Report Builder
Name	Description
Blocking work items by team (table and graph)	Shows a list of team work items that are blocking other work items. The graph shows blocking work items by the blocking team. This report does not show work items that block test cases.
Defects by priority and team (graph and table)	Shows a graph of open defects, grouped by priority and team. The table groups defects by project, priority, and team, and shows details about each defect.
Defects per requirement (graph and table)	Compares the number of open and closed defects (linked to requirements) that were found during testing, grouped by requirements.
Defects per test case (graph and table)	Compares the number of open and closed defects that are linked to test cases.
Incomplete stories (table and graph)	Shows the incomplete stories for specific iterations. The table is grouped by team and planned iteration. The graph shows the number of work items per team.
Iteration status of stories and defects	Lists the status of stories and defects for specific iterations. The table is grouped by iteration, team, and type.
Release status of stories and defects	Lists the status of stories and defects for a release. The table is grouped by iteration, team, and type.
Requirement traceability and test status	Lists requirements by collection or module with traceability or gaps to stories and test cases, as well as the results of testing.
Story status by iteration (graph and table)	Shows a graph or table of the open and closed stories for a release, with links to open defects.
Story traceability to test cases and defects	Lists open user stories with traceability or gaps to test cases, as well as the number of open defects from testing.
Test cases per requirement (table and graph)	Lists the total number of test cases per requirement, with links to test cases.
Work items blocked by other teams	Lists the team's work items that depend on other teams' open work items, ordered by name and severity.

Feedback