This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

6.2.1. Editing an Existing Incident

If you are editing an existing incident, the fields that are available and the fields that are required will depend on your stage in the incident workflow. For example an open incident might not require a “Resolved Version” whereas a resolved incident could well do. The types of change allowed and the email notifications that are sent will depend on how your project administrator has setup the system for you. Administrators should refer to the SpiraTeam Administration Guide for details on configuring the incident workflows to meet their needs.

Depending on the user’s role and whether they are listed as the owner or detector of the incident or not, displayed in the left hand side of the page, above the navigation list is a set of allowed workflow operations:

These workflow transitions allow the user to move the incident from one status to another. For example when the incident is in the Assigned status, you will be given the options to:

  • Resolve the Incident – changes status to “Resolved”
  • Unable to Reproduce – changes the status to “Not Reproducible”
  • Duplicate Incident - changes the status to “Duplicate”

After changing the status of the incident by clicking on the workflow link, you can then fill in the additional fields that are now enabled and/or required. Once you’ve made the changes to the appropriate incident fields, you can either click <Save>, <Save and Close>, or <Save and New> to commit the changes or <Refresh> to discard the changes and reload the incident from the database. In addition you can print the current incident by clicking <Print>, which will display a printable version of the page in a separate window.