Skip to content

Commit 745bf09

Browse files
author
Richard Jones
committed
*** empty log message ***
1 parent 8e574d9 commit 745bf09

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

doc/installation.txt

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Installing Roundup
33
==================
44

5-
:Version: $Revision: 1.69 $
5+
:Version: $Revision: 1.70 $
66

77
.. contents::
88

@@ -507,11 +507,13 @@ multiple trackers, which involve additional URLs, user databases, email
507507
addresses, databases to back up, etc.
508508

509509
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`_.
511512
2. Do you want to track internal software development issues and customer
512513
support issues separately? You can just set up an additiona "issue"
513514
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`_.
515517

516518

517519
Platform-Specific Notes
@@ -611,6 +613,10 @@ Next: `User Guide`_
611613
.. _`roundup specification`: spec.html
612614
.. _`tracker configuration`: customizing.html#tracker-configuration
613615
.. _`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
614620
.. _`customising roundup`: customizing.html
615621
.. _`upgrading document`: upgrading.html
616622
.. _`administration guide`: admin_guide.html

0 commit comments

Comments
 (0)