CA Agile Central provides powerful reporting capabilities to track your team's progress with standard reports on the Reports tab

A main navigation heading in CA Agile Central. Each tab contains several pages, which display various data. CA Agile Central tabs are My Home, Plan, Track, Quality, Portfolio Items, and Reports.

. You can also create custom reports based on your development data to make fact-based, informed decisions. There is no limit to the number of custom reports you can create.

Two custom report types are available:

• Work items

  Items which help define the project, or team objective. Work items in CA Agile Central are user stories, tasks, portfolio items, test cases, test sets, test case results, defects, and defect suites.

• Timesheets
  Timesheet reports require the Time Tracker module

  Modules are sets of advanced features included with the Unlimited Edition of CA Agile Central. Specific modules may be purchased for Enterprise Edition subscriptions. Time tracking, product, and portfolio management, advanced test management, and advanced security are some of the features provided by modules.

  enabled in your subscription

  An agreement to give a set of named users access to use the CA Agile Central service.

  .

Custom reports are based on the current project

A container for a set of releases and iterations, and their related user stories and tasks. In CA Agile Central, it is helpful to think of projects as work areas for teams. When using CA Agile Central Portfolio Manager, projects represent either work areas for portfolio and product managers or work areas for teams.

and any additional filters you define in the custom report definition. If you choose filters with values partially or wholly outside the scoped project, you may generate incomplete or blank reports. The list of data to report and the list of available filters are limited to information common to defects, stories, and test cases.

You can save custom reports on the Reports page

A location in CA Agile Central under any of the main navigation pages, that provides summary views of work item data. You can also create custom pages under CA Agile Central tabs. Custom pages are used to host one or many apps and can be copied, shared, and customized.

, save as .pdf, .jpg, or .csv formats, email them to other users, or print with annotations. You can also edit or delete custom reports from the Reports page. You can share custom reports with other users for viewing or editing, or they can be kept private.

To create a new custom report:

1. Select the Reports tab.
   Custom reports are listed in the right column with respective icons for private and shared reports.
2. Select +Add New in the upper-right corner.
   
3. From the Type drop-down, select the type of report.
4. From the I want to see drop-down, select a value. Add more values as needed.
5. From the Broken down by drop-down, specify how the data should be grouped in the report. Add more values as needed.
   Test case fields, defect fields, and all custom fields (except text-type) are allowed.
6. Optionally, select filter criteria to narrow the report results.
   You can select one value for each field to filter, setting different value criteria for each or select the filter value dynamically for iteration

   A theme-driven timebox of requests to be worked on and accepted within a release of a product; it is defined in an iteration planning meeting and is completed with an iteration demo and review meeting. The terms iteration and sprint are used synonymously.

   , release

   A timebox where work occurs in support of an internal or external delivery of a working, tested version of the system or software. In scrum, a release consists of multiple iterations to deliver new system code.

   , or tag

   A unique identifier that may be applied to a work item to indicate category or class. You may use tags as a filter to find specific sets of work items on summary pages.

   filters. Test case fields, defect fields, and all custom fields (except text-type) are allowed.
7. Select Run.
   From the report preview, you can save the report, email it to others, or save it as .pdf, .jpg, or .csv formats.

To save a custom report:

1. Run the report and select Save in the upper-right corner.
2. Name the report and add a brief description.
3. Select one of the following options for the report visibility:
   • Just me: The report will only be visible to you.
   • Anyone can view: The report will be visible (read-only) to everyone.
   • Anyone can view, edit, or delete: The report will be visible to everyone and anyone can edit or delete the report.

The custom report is added to your list of custom reports on the Reports tab.

Sample Custom Reports

For the number of stories versus the number of defects (and associated points

The most common units used by agile teams to estimate relative size of stories or portfolio items such as features and initiatives.

) scheduled in a release across multiple teams, select:

• I want to see: Count of Work Items
• Broken down by: Project and then by Type
• Filters: Release = <Release Name> or [Choose Dynamically]

For the work remaining to deliver a release feature

An improvement or capability of value to a stakeholder that can be developed in a PSI or release timebox (usually 10-12 weeks).

(when feature is identified by tag), select:

• I want to see: Sum of Task

  A unit of work that, when performed, contributes to the fulfillment and completion of a scheduled user story within the iteration. Tasks allow decomposition of stories into manageable units of work. Team members can take responsibility and ownership for each task, providing estimates and work left to do for completion.

  Estimate, Sum of Task To Do

  The amount of remaining effort required to complete a task. Generally recorded in hours.

• Broken down by: Tags and then by Project
• Filter: Tags = <Feature Tag> AND Release = <Release Name>

For blocked work (stories, defects, test cases) for a specific iteration, select:

• I want to see: Sum of Plan Estimate

  The amount of effort estimated to complete a single user story. Plan estimates are represented by points, t-shirt sizes, or other systems. They do not correspond to task or man hours.

• Broken down by: Schedule State

  A condition during the life of a work item where it satisfies given criteria. Examples include defined, in-progress, completed, open, closed, released, and so on.

  and by Type
• Filter: Schedule State = In-Progress AND Blocked =Yes AND Iteration = <Iteration Name>

For time spent working on a feature during a release, select:

• I want to see: Sum of Time Spent
• Broken down by: Work Item
• Filter: Release = <Release Name> AND Package = <Package value> AND Work Item Type = Story