Mercurial > p > roundup > code
comparison doc/customizing.txt @ 3289:5da323b46907
doc fix
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 14 Apr 2005 01:30:45 +0000 |
| parents | 3124e578db02 |
| children | bb08ffc56967 |
comparison
equal
deleted
inserted
replaced
| 3287:7a7f7d3a038d | 3289:5da323b46907 |
|---|---|
| 1 =================== | 1 =================== |
| 2 Customising Roundup | 2 Customising Roundup |
| 3 =================== | 3 =================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.177 $ | 5 :Version: $Revision: 1.178 $ |
| 6 | 6 |
| 7 .. This document borrows from the ZopeBook section on ZPT. The original is at: | 7 .. This document borrows from the ZopeBook section on ZPT. The original is at: |
| 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx | 8 http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx |
| 9 | 9 |
| 10 .. contents:: | 10 .. contents:: |
| 3196 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 3196 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 3197 | 3197 |
| 3198 Sometimes you will want to track different types of issues - developer, | 3198 Sometimes you will want to track different types of issues - developer, |
| 3199 customer support, systems, sales leads, etc. A single Roundup tracker is | 3199 customer support, systems, sales leads, etc. A single Roundup tracker is |
| 3200 able to support multiple types of issues. This example demonstrates adding | 3200 able to support multiple types of issues. This example demonstrates adding |
| 3201 a customer support issue class to a tracker. | 3201 a system support issue class to a tracker. |
| 3202 | 3202 |
| 3203 1. Figure out what information you're going to want to capture. OK, so | 3203 1. Figure out what information you're going to want to capture. OK, so |
| 3204 this is obvious, but sometimes it's better to actually sit down for a | 3204 this is obvious, but sometimes it's better to actually sit down for a |
| 3205 while and think about the schema you're going to implement. | 3205 while and think about the schema you're going to implement. |
| 3206 | 3206 |
| 3207 2. Add the new issue class to your tracker's ``schema.py`` - in this | 3207 2. Add the new issue class to your tracker's ``schema.py``. Just after the |
| 3208 example, we're adding a "system support" class. Just after the "issue" | 3208 "issue" class definition, add:: |
| 3209 class definition, add:: | 3209 |
| 3210 | 3210 # list our systems |
| 3211 system = Class(db, "system", name=String(), order=Number()) | |
| 3212 system.setkey("name") | |
| 3213 | |
| 3214 # store issues related to those systems | |
| 3211 support = IssueClass(db, "support", | 3215 support = IssueClass(db, "support", |
| 3212 assignedto=Link("user"), topic=Multilink("keyword"), | 3216 assignedto=Link("user"), topic=Multilink("keyword"), |
| 3213 status=Link("status"), deadline=Date(), | 3217 status=Link("status"), deadline=Date(), |
| 3214 affects=Multilink("system")) | 3218 affects=Multilink("system")) |
| 3215 | 3219 |