Mercurial > p > roundup > code
comparison doc/customizing.txt @ 3288:2e143b885cd7 maint-0.8
doc fix
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 14 Apr 2005 01:30:45 +0000 |
| parents | ca122bc16277 |
| children | 3b03f0981f4d |
comparison
equal
deleted
inserted
replaced
| 3286:239566bf5d33 | 3288:2e143b885cd7 |
|---|---|
| 1 =================== | 1 =================== |
| 2 Customising Roundup | 2 Customising Roundup |
| 3 =================== | 3 =================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.161.2.13 $ | 5 :Version: $Revision: 1.161.2.14 $ |
| 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:: |
| 3193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 3193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 3194 | 3194 |
| 3195 Sometimes you will want to track different types of issues - developer, | 3195 Sometimes you will want to track different types of issues - developer, |
| 3196 customer support, systems, sales leads, etc. A single Roundup tracker is | 3196 customer support, systems, sales leads, etc. A single Roundup tracker is |
| 3197 able to support multiple types of issues. This example demonstrates adding | 3197 able to support multiple types of issues. This example demonstrates adding |
| 3198 a customer support issue class to a tracker. | 3198 a system support issue class to a tracker. |
| 3199 | 3199 |
| 3200 1. Figure out what information you're going to want to capture. OK, so | 3200 1. Figure out what information you're going to want to capture. OK, so |
| 3201 this is obvious, but sometimes it's better to actually sit down for a | 3201 this is obvious, but sometimes it's better to actually sit down for a |
| 3202 while and think about the schema you're going to implement. | 3202 while and think about the schema you're going to implement. |
| 3203 | 3203 |
| 3204 2. Add the new issue class to your tracker's ``schema.py`` - in this | 3204 2. Add the new issue class to your tracker's ``schema.py``. Just after the |
| 3205 example, we're adding a "system support" class. Just after the "issue" | 3205 "issue" class definition, add:: |
| 3206 class definition, add:: | 3206 |
| 3207 | 3207 # list our systems |
| 3208 system = Class(db, "system", name=String(), order=Number()) | |
| 3209 system.setkey("name") | |
| 3210 | |
| 3211 # store issues related to those systems | |
| 3208 support = IssueClass(db, "support", | 3212 support = IssueClass(db, "support", |
| 3209 assignedto=Link("user"), topic=Multilink("keyword"), | 3213 assignedto=Link("user"), topic=Multilink("keyword"), |
| 3210 status=Link("status"), deadline=Date(), | 3214 status=Link("status"), deadline=Date(), |
| 3211 affects=Multilink("system")) | 3215 affects=Multilink("system")) |
| 3212 | 3216 |