[rt-users] Custom field values based on queue?

[Ruslan Zakirov]

What Kevin describes works. However, search by such CFs is slow if you don't
qualify queue in TicketSQL. Yes, there is a long form of query where you
define not only CF name, but also queue of the CF.

Such setup is used in RTIR for State custom field that is going to be
replaced by lifecycles.

Another way is to implement custom CF type, but this involves programming.

Regards, Ruslan. From phone.
09.09.2011 4:58 пользователь "Kevin Falcone" <falcone at bestpractical.com>
написал:
> On Thu, Sep 08, 2011 at 11:55:49PM +0200, Jim Lesinski wrote:
>> Ok that seems odd to me. How do you distinguish the field then if you
want to access it via API or other methods like controls by email?
>
> RT::CustomField->LoadByName is documented to expect a Queue, you can
> read about it in the perldoc.
>
> Extensions should load the CF off the ticket's queue.
>
> -kevin
>
>> Maybe the description can be used to determine the field
>> In the ui?
>>
>> Thanks,
>> Jim Lesinski
>>
>> On Sep 8, 2011, at 11:14 PM, Kevin Falcone <falcone at bestpractical.com>
wrote:
>>
>> > On Thu, Sep 08, 2011 at 10:42:27PM +0200, Jim Lesinski wrote:
>> >> Is it possible to base custom field values on the queue? I see that
>> >> you can have cascading drop down lists based on a previously
>> >> selected custom field value. I'd like the same thing but starting at
>> >> the queue level.
>> >
>> > Custom Fields can be assigned on a queue vs global basis, so just
>> > create one for each queue with different values.
>> >
>> > They're allowed to have the same name in each queue, but you may find
>> > it a bit confusing if you're writing code around it and forget to
>> > specify a queue.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110910/2f1068f9/attachment.htm>