From 647218a78b006b000c62dd95488eff7cae0bbe6d Mon Sep 17 00:00:00 2001
From: richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2>
Date: Mon, 16 Sep 2002 02:07:44 +0000
Subject: [PATCH] more doc, "fixer" example

git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1171 57a73879-2fb5-44c3-a270-3262357dd7e2
---
 doc/customizing.txt | 48 ++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 47 insertions(+), 1 deletion(-)

diff --git a/doc/customizing.txt b/doc/customizing.txt
index e6c8b1e..a7c9c81 100644
--- a/doc/customizing.txt
+++ b/doc/customizing.txt
@@ -2,7 +2,7 @@
 Customising Roundup
 ===================
 
-:Version: $Revision: 1.35 $
+:Version: $Revision: 1.36 $
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
    http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -652,6 +652,16 @@ the tracker **html** directory. There are several types of files in there:
 **style.css**
   a static file that is served up as-is
 
+Note: Remember tyhat you can create any template extension you want to, so 
+if you just want to play around with the templating for new issues, you can
+copy the current "issue.item" template to "issue.test", and then access the
+test template using the ":template" URL argument::
+
+   http://your.tracker.example/tracker/issue?:template=test
+
+and it won't affect your users using the "issue.item" template.
+
+
 How the templates work
 ----------------------
 
@@ -1808,6 +1818,42 @@ Alter the issue.item template section for messages to::
   </tal:block>
  </table>
 
+Restricting the list of users that are assignable to a task
+-----------------------------------------------------------
+
+1. create a new Role, say "Developer"::
+
+     db.security.addRole(name='Developer', description='A developer')
+
+2. create a new Permission, say "Fixer", specific to "issue"::
+
+     p = db.security.addPermission(name='Fixer', klass='issue',
+         description='User is allowed to be assigned to fix issues')
+
+3. assign the new Permission to your "Developer" Role::
+
+     db.security.addPermissionToRole('Developer', p)
+
+4. use the new Permission in restricting the "assignedto" list in the issue
+   item edit page::
+
+    <select name="assignedto">
+     <option value="-1">- no selection -</option>
+     <tal:block tal:repeat="user db/user/list">
+     <option tal:condition="python:user.hasPermission('Fixer', context.classname)"
+             tal:attributes="value user/id;
+                             selected python:user.id == context.assignedto"
+             tal:content="user/realname"></option>
+     </tal:block>
+    </select>
+
+For extra security, you may wish to overload the hasEditItemPermission method
+on your tracker's interfaces.Client class to enforce the Permission
+requirement::
+
+XXX
+
+
 -------------------
 
 Back to `Table of Contents`_
-- 
2.30.2