Yes, it is.
You only have to define the custom field (Configuration->Custom Fields)
and ensure that it “Applies to” “Tickets” when you create or modify it.
Then go to the link “Applies to” just above, in the upper menu bar, and
check the queues where you want to apply the custom field.
Alternatively, you can perform this second step in the queue
configuration (Configuration -> Queues -> [Queue Name]-> Ticket Custom
Field) and check the custom fields that you want to apply to this queue.
So it works for me in RT 3.8.4.
Rich West wrote:
By correct result, I meant that it would do what I was trying for:
o Custom Field associated to all tickets regardless of queue
o Custom field associated to all tickets in queue A
o Custom field associated to all tickets in queue B
Is this possible?
On Wed, 08 Jul 2009 14:06:54 -0700, Kevin Gagel wrote: I’m not sure what
you mean by correct result. But I recently figured out a problem I was
having with queues and custom fields. Mine related more to a dashboard’s
ability to see the custom field. It seems that if the custom field is a
queue only field then the dashboard cannot be setup to show a column using
that custom field. On the other hand if the custom field is setup as a
global field it shows up readily as choice for a column to be picked as
displayable in the dashboard.
I’ve setup my install so that custom fields intended for a queue are only
there and ones that should be in all queues are globally setup. Perhaps
that is what you need to do…
Community help: http://wiki.bestpractical.com
Commercial support: firstname.lastname@example.org
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Spam detection software, running on the system “hal.ific.uv.es”, has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn’t spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: By correct result, I meant that it would do what I was
trying for: o Custom Field associated to all tickets regardless of
queue o Custom field associated to all tickets in queue A o Custom
field associated to all tickets in queue B […]
Content analysis details: (5.5 points, 5.0 required)
pts rule name description
2.5 FORGED_RCVD_HELO Received: contains a forged HELO
3.0 KXLINKRR_BODY BODY: Body contains suspicious link
| __ __ | Carlos Garcï¿½a Montoro Ingeniero Informï¿½tico
|_Y/| Instituto de Fï¿½sica Corpuscular Centro Mixto CSIC - UV
|_] [/| Servicios Informï¿½ticos
|  | Edificio Institutos de Investigaciï¿½n email@example.com
|C S I C| Apartado de Correos 22085 E-46071 Valencia Tel: +34 963543706
|______| Espaï¿½a / Spain Fax: +34 963543488
cgarcia.vcf (441 Bytes)