From 64076d6eeebe4ec829dd567bdc0c03af3c851f6a Mon Sep 17 00:00:00 2001 From: richard Date: Tue, 30 Mar 2004 06:23:11 +0000 Subject: [PATCH] *** empty log message *** git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@2231 57a73879-2fb5-44c3-a270-3262357dd7e2 --- doc/installation.txt | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/doc/installation.txt b/doc/installation.txt index 793b543..4408219 100644 --- a/doc/installation.txt +++ b/doc/installation.txt @@ -2,7 +2,7 @@ Installing Roundup ================== -:Version: $Revision: 1.69 $ +:Version: $Revision: 1.70 $ .. contents:: @@ -507,11 +507,13 @@ multiple trackers, which involve additional URLs, user databases, email addresses, databases to back up, etc. 1. Do you want a tracker per product you sell/support? You can just add - a new property to your issues called Product, and filter by that. + a new property to your issues called Product, and filter by that. See + the customisation example `adding a new field to the classic schema`_. 2. Do you want to track internal software development issues and customer support issues separately? You can just set up an additiona "issue" class called "cust_issues" in the same tracker, mimicing the normal - "issue" class, but with different properties. + "issue" class, but with different properties. See the customisation + example `tracking different types of issues`_. Platform-Specific Notes @@ -611,6 +613,10 @@ Next: `User Guide`_ .. _`roundup specification`: spec.html .. _`tracker configuration`: customizing.html#tracker-configuration .. _`customisation documentation`: customizing.html +.. _`Adding a new field to the classic schema`: + customizing.html#adding-a-new-field-to-the-classic-schema +.. _`Tracking different types of issues`: + customizing.html#tracking-different-types-of-issues .. _`customising roundup`: customizing.html .. _`upgrading document`: upgrading.html .. _`administration guide`: admin_guide.html -- 2.30.2