A customer asked is how they could run a report on a daily basis to see for how long a defect has been assigned to a specific status and the audit log of the status changes. That is best done by using the History table and the main Incident table together in a custom report
Spira currently limits the statuses available for the requirement artifact due to the support the requirement status level automation. One request, despite infrequent, is to address how to accommodate excluding requirements at a release level or reporting on requirements in this 'required but currently unavailable' requirement status. This article addresses this requirement.
A customer recently asked for assistance requirement documentation on the Inflectra website about help on the various fields available when creating requirements in Spira.
Specifically, the columns such as Type (List of values = Design element, Epic, Feature, Need, Quality, Use Case, User Story). They needed to understand what was the intended use of each of these fields. and also the meaning of list of values under the status fields (Planned, Requested, developed etc). They wanted to see if we could provide a more detailed explanation or guide what each list of values means? They did not want to make any incorrect assumptions.
Sometimes customers need to show a Graph with all the Test Runs by status for a specific Release in Spira. This article explains how to use the custom graphing engine to achieve this.
Sometimes customers need to show a Graph with all the Incidents by status for a specific Component in Spira. This article explains how to use the custom graphing engine to achieve this.
The incidents in Spira are able to have customizable incident types, statuses, priorities and severities. This means that each project has unique IDs for the various attributes. Sometimes when you incorrectly load in data using our Excel Add-In, you can link incidents to attributes from other projects. This article describes the problem and the solution.
One of the limitations in SpiraTest and SpiraTeam v4.x was that for performance reasons we could not handle test sets with very large numbers of test cases and that the system was not able to display the counts of the test cases and the execution status for test set folders.