Spira 4.2 User Manual Help Viewer
SpiraTeam® provides the ability to create, edit, assign, track, manage and close incidents that are raised during the testing of the software system under development. These incidents can be categorized into bugs, enhancements, issues, training items, limitations, change requests, and risks, and each type has its own specific workflow and business rules. Typically each incident is raised initially as a ‘New’ item of type ‘Incident’. Following the review by the project manager and customer, they are changed to one of the other specific types, given a priority (critical, high, medium or low), and status changed to ‘Open’. Once it is assigned to a developer for fixing, it is changed to status ‘Assigned’.
The developer now works to correct the incident, after which time its status changes to ‘Fixed’ or ‘Not Reproducible’ depending on the actions taken (or not taken). Finally the project manager and customer verify that it has indeed been fixed, and the status is changed to ‘Closed’. SpiraTeam® provides robust sorting and filtering of all the incidents in the system, as well as the ability to view the incidents associated with particular test cases and test runs, enabling drill-down from the requirements coverage display, right through to the open incidents that are affecting the requirement in question.