Status Charts

Use the following charts to track iteration or release status:

You can add these charts as custom pages.

Defect Arrival and Kill Rate chart

The Defect Arrival and Kill Rate chart shows the high-level status of active defects per project along with daily open and kill rates to enable you to see trends in the quality assurance process. This chart reflects only those defects contained in the displayed project.

This chart has three tabs. The following details are included in each tab of this chart:

Arrival and Kill

  • All active defects. Active is defined as any defects with a state other than "Closed".
  • The defect arrival rate. Arrival rate is defined as all defects that are opened per day.
  • The defect kill rate. Kill rate is defined as all defects that have been closed (State = "Closed") per day.

Priority

  • Any custom Priority values that have been configured for your workspace

State

  • Any custom State values that have been configured for your workspace

Regardless of chart chosen, all workdays contained within the past 30 days (on the Dates axis)

Hover over any chart bar or line position to display the exact number of defects in each state per workday. The workdays displayed in the dates axis are determined by your subscription administrator when setting up your workspace.

The header displays the start and end dates of the iteration.

Click anywhere on the mini Defect Arrival and Kill Rate chart to display the full-sized chart. From the full-sized chart you can click the Priority or State link in the upper-right corner to display those charts.

Defects by Priority chart

The Defects by Priority chart displays active (not closed) defects categorized by priority over time. Use this chart to identify defect priority trends such as a spike in the number of P1 defects or a general decrease in the number of overall defects. The data is displayed as a stacked column where each priority value is represented by a different color.

The x-axis indicates the time period for the data above. By default, it displays all workdays contained within the past 30 days. However, you can change the date range and granularity (weeks, months, quarters) by adding the report as an app on your dashboard.

To conserve space, there are no legends on the dashboard versions. Hover over a section of a bar to view its label and the exact number of defects in each priority for that time period.

You can drag the chart to your desktop or other location to save a .png version of the chart.

Like most of the charts, your project scope will determine which defects are included.

Technical details:

  • Data for this report is only available back to January 2010.
  • The x-axis label represents the moment-in-time values for the last day of the interval. If your report is in months, then the points above the label 6/2011 are the moment-in-time values as of midnight 6/30/2011.
  • When priority or severity filters are applied on the dashboard version, the moment-in-time values (as opposed to the current values) are used to determine what data is included. For example, if you chose to only include high priority defects and a defect started out as a high priority but later changed to a lower priority, it would be included in the earlier columns on the chart but excluded from the later columns.

Defects by State chart

The Defects by State chart displays active (not closed) defects categorized by state over time. Use this chart to identify defect state trends such as a spike in the number of unassigned defects or a general decrease in the number of open defects.

The data displays as a stacked column where each state value is represented by a different color. The x-axis indicates the time period for the data above. By default, it displays all workdays contained within the past 30 days. However, you can change the date range and granularity (weeks, months, quarters) by adding the report as an app on your dashboard.



To conserve space, there are no legends on the dashboard versions. Hover over a section of a bar to view its label and the exact number of defects in each priority for that time period.

You can drag the chart to your desktop or other location to save a .png version of the chart.

Like most of the charts, your project scope will determine which defects are included.

Technical details:

  • Data for this report is only available back to January 2010.
  • The x-axis label represents the moment-in-time values for the last day of the interval. If your report is in months, then the points above the label 6/2011 are the moment-in-time values as of midnight 6/30/2011.
  • When priority or severity filters are applied on the dashboard version, the moment-in-time values (as opposed to the current values) are used to determine what data is included. For example, if you chose to only include high priority defects and a defect started out as a high priority but later changed to a lower priority, it would be included in the earlier columns on the chart but excluded from the later columns.

Defect Trend chart

The Defect Trend chart displays the cumulative defects activated (opened) versus cumulative terminated (closed) over time.

The chart displays the rate at which defects are being activated (red series), the rate at which defects are being terminated (green series), and the trend for the total number of active defects (black series). The net change in total active defects for the displayed time frame displays at the top of the default chart.

You can drag the chart to your desktop or other location to save a .png version of the chart.

defect trend

To conserve space, there are no legends in the app versions of this chart.

Technical details:

  • Data for this report is only available back to January 2010.
  • The x-axis label represents the moment-in-time values for the last day of the interval. If your report is in months, then the points above the label 6/2011 are the moment-in-time values as of midnight 6/30/2011.
  • The cumulative terminated and total active series are calculated directly from the data. However, the cumulative activated series is calculated by subtracting the total active from the cumulative terminated. This is done to ensure that the information is consistent across the series. If it were calculated directly and a severity or priority filter were applied, then any changes to the severity or priority that occurred between the activation and termination events would result in an inconsistency. It might be counted in the activated series but not in the terminated series. For example, you only want the report to run for High Priority defects. This approach assures that it is removed from the cumulative activated series the moment that the Priority field is changed from high to low.

Build Health chart

The Build Health chart characterizes your software builds over the last 30 days.

The chart helps you detect trends and consider questions like:

  • How often does the build fail?
  • When does build quality decline? Is it at end of a release cycle?
  • Is the length of the build getting too long?
  • Should we move some tests to run each night?
build health

For each day, you can see the number of builds with a successful, failed, incomplete, or unknown status, and the average build duration in seconds. Hover over any colored portion of the iteration bar to see the total number of builds for the corresponding status.

Builds are identified by looking both up and down your project hierarchy, regardless of your project scope setting. This supports the organization of a project or product line with teams that share the same build definitions and SCM repositories. Watch Understanding the Project Hierarchy or see Set Up Your Project Hierarchy to learn how to organize projects and teams in Rally.

Note: A status of Unknown may indicate a problem with an external program called during the build process. Check to see if the program hangs (reporting back nothing), or if it reports back something that your build script is not designed to handle.

Top Files by Changes chart

The Top Files by Changes chart helps you identify the files in your repository that experience the most revisions over the last 30 days.

The chart helps you consider questions like:

  • Which files are candidates for decomposition?
  • Should there be additional testing around specific files?
  • Where should we start when making changes in our code base?

The chart shows the top ten files with changes (from highest to lowest number of changes) and a cumulative percentage line. There is no time component; all files in the repository with changes are represented.

Files in the entire SCM repository are included for your workspace, regardless of your project scope setting. This supports the organization of a project or product line with sub-teams that share the same build definitions and SCM repositories. Watch Understanding the Project Hierarchy or see Set Up Your Project Hierarchy to learn how to organize projects and teams in Rally.

Note: The second-to-last point on right side of the cumulative percentage line is often the most interesting. If it is a high percentage of change, it could be valuable to refactor or decompose those files. If it is a low percentage, improving those files may not be the most effective way to impact maintainability.

Top Files by Defects chart

The Top Files by Defects chart helps you determine which files in your repository have the most associated defects.

The chart helps you consider questions like:

  • Which files are the most problematic?
  • Are any files candidates for refactoring?
  • Should there be automated tests around specific files?
top defects

The chart shows the top ten files with defects (from the highest to lowest number of defects) and a cumulative percentage line. There is no time component; all files in the repository with defects are represented.

This chart shows only files associated with defects within your project scope.

Note: The second-to-last point on right side of the cumulative percentage line is often the most interesting. If it is a high percentage of defects, it could be valuable to refactor or decompose those files. If it is a low percentage, improving those files may not be the most effective way to impact overall quality.

Feedback

Need more help? The Rally Community is your one-stop shop for self-service and support. To submit feedback or cases to Rally Support, find answers, and collaborate with others, please join us at rallycommunity.rallydev.com.
© 2015 Rally Software Development Corp | Legal