Inside SpiraTeam (or SpiraTest, SpiraPlan), you have the following built-in incident aging graph:

Sometimes you want to be able to generate an incident aging report that lets you have more fine-grained control over the data.

Custom Incident Aging Report

If you use the Spira custom reporting engine, the following ESQL will create a list of open incidents in the current project with the number of days open (i.e age in days) displayed in a column to the right:

select INC.INCIDENT_ID, INC.NAME, DiffDays(INC.CREATION_DATE, CurrentDateTime()) as AGING_DAYS from SpiraTestEntities.R_Incidents as INC where INC.PROJECT_ID = ${ProjectId}
order by AGING_DAYS desc

When you use the Create Default Template option, Spira will create the following table for you:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl">
  <xsl:template match="/RESULTS">
    <table class="DataGrid"><tr><th>INCIDENT_ID</th><th>NAME</th><th>AGING_DAYS</th></tr>
      <xsl:for-each select="ROW">
        <tr><td><xsl:value-of select="INCIDENT_ID"/></td><td><xsl:value-of select="NAME"/></td><td><xsl:value-of select="AGING_DAYS"/></td>

When you generate the report, you will get the following data:

1Cannot log into the application5637
2Not able to add new author5637
3Clicking on link throws fatal error5637
4Database not backing up correctly5636
5Cannot install system on Oracle 9i5636
6The book listing screen doesn't sort5636
7Cannot add a new book to the system5634
8Editing the date on a book is clunky5634
9Editing the date on an author is clunky5634
18Ability to integrate with other systems5621


You can change the report to display data for all projects, a single program, a specific release, or group of releases by adjusting the WHERE clause part.