|
2 | 2 | Installing Roundup |
3 | 3 | ================== |
4 | 4 |
|
5 | | -:Version: $Revision: 1.69 $ |
| 5 | +:Version: $Revision: 1.70 $ |
6 | 6 |
|
7 | 7 | .. contents:: |
8 | 8 |
|
@@ -507,11 +507,13 @@ multiple trackers, which involve additional URLs, user databases, email |
507 | 507 | addresses, databases to back up, etc. |
508 | 508 |
|
509 | 509 | 1. Do you want a tracker per product you sell/support? You can just add |
510 | | - a new property to your issues called Product, and filter by that. |
| 510 | + a new property to your issues called Product, and filter by that. See |
| 511 | + the customisation example `adding a new field to the classic schema`_. |
511 | 512 | 2. Do you want to track internal software development issues and customer |
512 | 513 | support issues separately? You can just set up an additiona "issue" |
513 | 514 | class called "cust_issues" in the same tracker, mimicing the normal |
514 | | - "issue" class, but with different properties. |
| 515 | + "issue" class, but with different properties. See the customisation |
| 516 | + example `tracking different types of issues`_. |
515 | 517 |
|
516 | 518 |
|
517 | 519 | Platform-Specific Notes |
@@ -611,6 +613,10 @@ Next: `User Guide`_ |
611 | 613 | .. _`roundup specification`: spec.html |
612 | 614 | .. _`tracker configuration`: customizing.html#tracker-configuration |
613 | 615 | .. _`customisation documentation`: customizing.html |
| 616 | +.. _`Adding a new field to the classic schema`: |
| 617 | + customizing.html#adding-a-new-field-to-the-classic-schema |
| 618 | +.. _`Tracking different types of issues`: |
| 619 | + customizing.html#tracking-different-types-of-issues |
614 | 620 | .. _`customising roundup`: customizing.html |
615 | 621 | .. _`upgrading document`: upgrading.html |
616 | 622 | .. _`administration guide`: admin_guide.html |
|
0 commit comments