From 083ff3885abfabc28ca7f068fd2b5385b685fd7b Mon Sep 17 00:00:00 2001
From: "lpsolit%gmail.com" <>
Date: Thu, 7 Feb 2008 05:36:38 +0000
Subject: =?UTF-8?q?Doc=20patch=20for=20bug=20101179=20(custom=20statuses?=
 =?UTF-8?q?=20and=20workflow)=20-=20Patch=20by=20Fr=C3=83=C2=A9d=C3=83?=
 =?UTF-8?q?=C2=A9ric=20Buclin=20<LpSolit@gmail.com>=20r=3DColin?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/xml/administration.xml | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

(limited to 'docs')

diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml
index 583042520..4bd33358c 100644
--- a/docs/xml/administration.xml
+++ b/docs/xml/administration.xml
@@ -2270,7 +2270,9 @@ foo: ENTRY, MANDATORY/MANDATORY, CANEDIT
       bug priorities and severities can be edited from the User Interface
       directly. This means that it is no longer required to manually edit
       <filename>localconfig</filename>. Starting with Bugzilla 2.23.3, you
-      can also customize the list of valid resolutions from the same interface.
+      can also customize the list of valid resolutions from the same interface,
+      and since Bugzilla 3.1.1 the list of valid bug statuses can be customized
+      as well.
     </para>
 
     <section id="edit-values-list">
@@ -2312,6 +2314,27 @@ foo: ENTRY, MANDATORY/MANDATORY, CANEDIT
     </section>
   </section>
 
+  <section id="bug_status_workflow">
+    <title>Bug Status Workflow</title>
+
+    <para>
+      The bug status workflow is no longer hardcoded but can be freely customized
+      from the web interface. Only one bug status cannot be renamed nor deleted,
+      UNCONFIRMED, but the workflow involving it is free. The configuration
+      page displays all existing bug statuses twice, first on the left for bug
+      statuses we come from and on the top for bug statuses we move to.
+      If the checkbox is checked, then the transition between the two bug statuses
+      is legal, else it's forbidden independently of your privileges. The bug status
+      used for the "duplicate_or_move_bug_status" parameter must be part of the
+      workflow as that is the bug status which will be used when duplicating or
+      moving a bug, so it must be available from each bug status.
+    </para>
+    <para>
+      When the workflow is set, the "View Current Triggers" link below the table
+      lets you set which transitions require a comment from the user.
+    </para>
+  </section>
+
   <section id="voting">
     <title>Voting</title>
 
-- 
cgit v1.2.1