--- a/doc/customizing.txt	Sun Mar 09 22:57:47 2003 +0000
+++ b/doc/customizing.txt	Sun Mar 09 23:03:06 2003 +0000
@@ -2,7 +2,7 @@
 Customising Roundup
 ===================
 
-:Version: $Revision: 1.76 $
+:Version: $Revision: 1.77 $
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
    http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -2186,7 +2186,14 @@
 Sometimes tracker admins want to control the states that users may move issues
 to.
 
-1. add a Multilink property to the status class::
+1. make "status" a required variable. This is achieved by adding the
+   following to the top of the form in the ``issue.item`` template::
+
+     <input type="hidden" name="@required" value="status">
+
+   this will force users to select a status.
+
+2. add a Multilink property to the status class::
 
      stat = Class(db, "status", ... , transitions=Multilink('status'), ...)
 
@@ -2195,7 +2202,7 @@
    a. through the web using the class list -> status class editor, or
    b. using the roundup-admin "set" command.
 
-2. add an auditor module ``checktransition.py`` in your tracker's
+3. add an auditor module ``checktransition.py`` in your tracker's
    ``detectors`` directory::
 
      def checktransition(db, cl, nodeid, newvalues):
@@ -2216,7 +2223,7 @@
      def init(db):
          db.issue.audit('set', checktransition)
 
-3. in the ``issue.item`` template, change the status editing bit from::
+4. in the ``issue.item`` template, change the status editing bit from::
 
     <th nowrap>Status</th>
     <td tal:content="structure context/status/menu">status</td>