RedmineIssueTrackingSetup » History » Version 3
Jean-Philippe Lang, 2007-10-12 21:26
| 1 | 1 | Jean-Philippe Lang | h1. Issue tracking system |
|---|---|---|---|
| 2 | |||
| 3 | h2. Issue statuses |
||
| 4 | |||
| 5 | h2. Workflow |
||
| 6 | |||
| 7 | The workflow lets you define status transitions that the various project members are allowed to make on the issues, according to their type. |
||
| 8 | |||
| 9 | On the workflow setup screen, select the role and the tracker for which you want to edit the workflow, then click 'Edit'. The screen lets you select the authorized transitions, for the chosen role and tracker. The Current Status options indicate the initial status of an issue. The "New Statuses allowed" columns stand for the statuses that can be applied. |
||
| 10 | |||
| 11 | Note: In order to allow a role to change the status of existing issues, you have to give him the 'Change issue status' permission (see [[RedmineRoles|Roles and permissions]]). |
||
| 12 | |||
| 13 | 3 | Jean-Philippe Lang | p=. !workflow_example.png! |
| 14 | 2 | Jean-Philippe Lang | |
| 15 | 1 | Jean-Philippe Lang | In the above example, Bugs with a New status could be given an Assigned or Resolved status by the Developer role. Those with an Assigned status could get a Resolved status. The status of all the other Bugs cannot be modified by the Developer. |