In my RT2 setup, I had hierarchical keywords, such as
Central Processing Unit
Alpha
AMD
Athlon
Intel
i386
i486
i586
i686
ia64
StrongARM
Mips
No Architecture
Not Applicable
…
It appears that in RT3 that the Custom Fields are flat judging by
the UI to enter values, so I’d have to do something like this:
Central Processing Unit
Alpha
AMD - Athlon
Intel - i386
Intel - i486
Intel - i586
Intel - i686
Intel - ia64
Intel - StrongARM
Mips
No Architecture
Not Applicable
…
Is this accurate?
Also, in this email thread
http://lists.fsck.com/pipermail/rt-devel/2002-November/002721.html
there’s the statement that Custom Field are more flexible than Keywords,
but there’s nothing stating how and why. Could we find out how they are
better?
Best,
Blair
Blair Zajac blair@orcaware.com
Plots of your system’s performance - Orca Home Page - OrcaWare Technologies