A workflow is used to define the life cycle of a task. In contrast to pipelines, a workflow is applied to a single task, as opposed to spawning a sequence of tasks. Workflows are mainly used for task sign off, user story testing, art sign off or quality iterations.
A simple workflow for a task which involves approval of quality
Setting a workflow on a task automatically progresses the workflow to the first workflow state. Going to the next status can be done manually, or can be triggered by changing the item status of the underlying item. Double-clicking the Status column will display a list of valid Item statuses, and workflow states, to which the item can progress.
Moving to the next state in a workflow by double-clicking the status column
Building a workflow
You build a workflow by inserting statuses and transitions shown here on the toolbar when editing.
Editing a Sign-off workflow
Workflow status settings
Jump to the next chapter if you want to know more about workflow status settings.
Exporting and importing workflows
Under the More.. menu you can export and import your workflows as XML. This is useful when transferring workflows between projects or databases.
Exporting and importing a workflow through the More menu
Workflow access rights
Users or user groups can be allowed to alter a workflow beyond the defined restrictions, giving them permission to edit the full item. This capability is set through the option Edit workflow access rights in the More menu.
For examples on using Workflow access rights, read Using workflows for testing user stories.
You can use workflows for testing completed tasks and user stories without delegating parts of the project or backlog.
This is useful when you want a group of testers to test user stories in the backlog without being able to change any property of the user story itself.
Setting access on workflow