Chart displays cumulative defects opened versus closed in a
against the total active defects during the same time period.
What it is
The Release Defect Trend chart 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) during the same time period.
How it is calculated
The chart looks at defects in
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"
for the total active count. Basically, the release's purpose is to provide the time frame.
The chart does not look at the
history. In the future, you can run analytics based on the revision history. See our Lookback API documentation for more information.
and all subsequent data being displayed obeys project scoping.
Cumulative Activated: Defect
OpenedDate for the selected Release.
Cumulative Terminated: Defect field ClosedDate for the selected Release.
Total Active: Count of all defects where State
The "Total Active" value counts non-closed defects based on the chart's project scoping activity during the release's
. 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.
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 computed separately.