Release Defect Trend

The
Release
Defect
Trend
app
allows you to view cumulative defects opened versus closed over the course of a release, showing whether the trend is increasing or decreasing. The chart visually shows the rate at which defects are being activated (red line), the rate at which defects are being terminated (green line) and the trend for the total number of active defects (black line).

To enable the legend for the app, select Settings, Show Legend and Save.

Data displayed in the app is in the same format as the Release Defect Trend chart. Select the chart to go to the Reportstab
, where you may view additional information including a key and summary metrics. You may also print, email, and export the chart from the Reports tab.

Collection Frequency

Midnight (
workspace
timezone)

How It Is Calculated

The chart looks at defects in
project
scope
during the time frame of the release. For "today" it looks for defects created today, defects closed today to get today's values for opened and closed, and all defects in project scope not in a "Closed"
state
for the total active count. Basically, the release's purpose is to provide the time frame.

The chart does not look at the
revision
history. In the future, you can run analytics based on the revision history. See our Lookback API documentation for more information.

Active Fields

Cumulative Activated: Defect
field
OpenedDate for the selected Release.
Cumulative Terminated: Defect field ClosedDate for the selected Release.
Total Active: Count of all defects where State < "Closed".

The "Total Active" value counts non-closed defects based on the chart's project scoping activity during the release's
timebox
. This means the count is not limited to defects scheduled during the particular release.

Also, multiple actions are being counted against a single defect. This then causes the cumulative defect count to be higher than what you have scheduled into the filtered release.

What About...

Q: So what happens if a defect was created (outside of the release), closed, then assigned to a release, re-opened, and then re-closed, would it appear on this chart?

A: When those things happened comes into play, but if it was closed today, it should show up in the Cumulative Terminated count for today. Timezones could also come into play here, too. Did the defect in question ever belong to a project that isn't in scope? The historical data is pulled from metrics collection run at midnight of the workspace timezone based on projects in scope so if it wasn't in scope when that processing was done, there wouldn't be an entry for it there. In that case, the "today's" value is calculated separately.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.