From 18001e5a5b14cae3a3852c1f9d3da9c014fe9fd3 Mon Sep 17 00:00:00 2001 From: Jean-Philippe Lang Date: Tue, 2 Jan 2007 14:56:10 +0000 Subject: various documentation updates git-svn-id: http://redmine.rubyforge.org/svn/trunk@141 e93f8b46-1217-0410-a6f0-8f06a7374b81 --- public/manual/en/ch01s07.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'public/manual/en/ch01s07.html') diff --git a/public/manual/en/ch01s07.html b/public/manual/en/ch01s07.html index 7b95d8a63..22bca99a3 100644 --- a/public/manual/en/ch01s07.html +++ b/public/manual/en/ch01s07.html @@ -1,3 +1,3 @@ - 7. EnumerationsredMine home

7. Enumerations

The value lists used by the application can be customized (for example, setting Issue priorities). This screen allows you to define the possible values for each of the following lists:

  • Issue Priorities

  • Document Categories

\ No newline at end of file + 7. Workflowredmine

7. Workflow

The workflow allows to define changes the various project members are allowed to make on the Issues, according to their type.

Select the role and the tracker for which you want to modify the workflow, then click Edit. The screen allows you then to modify the authorized change, for the chosen role and tracker. The Current Status options indicate the initial request status. The "New Statuses allowed" columns stand for the authorized status to apply.

Note: In order for a particular Role to change an Issue status, the authorization must be given to it explicitly, regardless of the workflow configuration.

In the above example, Bug type Issue requests 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 Bug type requests cannot be modified by the Developer.

\ No newline at end of file -- cgit v1.2.3