Custom Fields Search

RT Users
1

Greetings,

Is there a way to add a custom field to the search facility in RT3?

Thanks,

David Bauman

2

Hi David,

Is there a way to add a custom field to the search facility in RT3?

Global custom fields should appear in the search UI.

After you’ve chosen a queue (Queue = ‘General’, for instance), the
custom fields for the chosen queue will also be available for
searching via the search UI.

Linda

3

Duh, My apoligies for the stupid question.----- Original Message -----
From: “Linda Julien” julien@bestpractical.com
To: david@anet.com
Cc: rt-users@lists.fsck.com
Sent: Monday, January 26, 2004 12:55 PM
Subject: Re: [rt-users] Custom Fields Search

Hi David,

From: “David Bauman” david@anet.com
Date: Mon, 26 Jan 2004 12:44:56 -0600

Is there a way to add a custom field to the search facility in RT3?

Global custom fields should appear in the search UI.

After you’ve chosen a queue (Queue = ‘General’, for instance), the
custom fields for the chosen queue will also be available for
searching via the search UI.

Linda

rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

4

Hi,On Mon, 26.01.2004 at 13:55:36 -0500, Linda Julien julien@bestpractical.com wrote:

Global custom fields should appear in the search UI.

I have one, but entering data and hitting “search” doesn’t yield
results (despite I know they are there).
The field type is “enter multiple values” - ie, a long text field.

This is 3.0.8 + Pg 7.4.1 on Debian unstable.

Best,
–Toni++

5

Hi,On Thu, 26.02.2004 at 17:48:00 +0100, Toni Mueller support-rt@oeko.net wrote:

On Mon, 26.01.2004 at 13:55:36 -0500, Linda Julien julien@bestpractical.com wrote:

Global custom fields should appear in the search UI.
This is 3.0.8 + Pg 7.4.1 on Debian unstable.

yesterday I upgraded to 3.0.9, and the problem persists.

The idea is to group tickets by the custom field.

Although I’m not sure where the information is kept, there is a global
table “customfieldvalues” which is empty. I formerly had such custom
fields on a per-queue basis until I decided to have only a global one.
Therefore I disabled the per-queue fields and introduced the global
one (all with the same name, you guessed it).

Of course, I made sure to enter the data I can’t search for in this
field only after I modified the queue…

OT, but 3.0.9 seems to be a speed improvement over 3.0.8 again.

Best,
–Toni++