Workflow

A workflow defines how users can change issue statuses, based on a combination of trackers and roles.
For example, you can configure a workflow so that only users with the Manager role can mark issues in the Bug tracker as completed.
This allows you to tailor Redmine’s behavior to fit the structure and policies of your organization.

A workflow determines which status transitions are allowed for each tracker and role.
If no workflow is defined, users will not be able to change an issue’s status.

Each tracker has one workflow for every role defined in Redmine.
In other words, the total number of workflows equals the number of trackers multiplied by the number of roles.

You can view or modify workflows under
Administration → Workflows.

Example Configuration

The following example shows the default workflow settings for the Developer role in the Bug tracker.
When a user with the Developer role works on issues in the Bug tracker, the following restrictions apply:

  • The issue status cannot be changed to “New.”
  • The issue status cannot be changed to “Rejected.”
  • Issues with the status “Closed” or “Rejected” cannot have their status changed.
Workflow Example
← Back to Glossary Index