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

SpiraTest Administration Guide Help Viewer

1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices
Search:
1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices

3.4. Workflows

Clicking on the “Edit Workflows” link in the Administration sidebar navigation brings up the list of defined incident workflows for the current project. A workflow is a predefined sequence of incident statuses linked together by “workflow transitions” to enable a newly created incident to be reviewed, prioritized, assigned, resolved and closed, as well as to handle exception cases such as the case of a duplicate or non-reproducible incident. The workflow list screen for a sample project is illustrated below:

To modify the name, default status, notify and/or active flags, simply change the values in the appropriate text-box, radio-button, check-box or drop-down list and click the <Update> button. To add a new workflow, simply click the <Add> button and a new workflow will be created with the standard SpiraTeam® steps and transitions.

You can have as many workflows as you like in a project, but only one can be marked as the default. Each incident type is assigned to a workflow; this allows you to have different incident types follow different paths from creation of closure. However when a new incident type is created, it will be initially associated with the project’s default workflow. The steps and transitions that make up the default workflow are illustrated in the diagram below:

The notify flag is used to tell SpiraTeam® whether that particular workflow should have email notifications turned on or off. You define what transitions and which recipients should receive the emails in the workflow transition editor (see below), but you can globally turn on/off notifications here as well. This is useful if you find that the notifications are becoming an annoyance, or if the email server is unavailable for a period of time.

Note: You can only assign an active workflow to an incident type, and similarly you cannot make a workflow inactive that is currently linked to an incident type. This is important as all incident types need to be linked to an active workflow at all times.