[rt-users] (Very) Low-level CF question

[Kenneth Crocker]

Joe,


	Hypothetical situations could involve endless debate, especially if 
they are based on an unrealistic scenario. Not to offend nor sound too 
incredulous, but why would anyone name ANY custom fields the same names 
for different applications/uses? Why not just prefix the "queue-based" 
Custom field with the queue name "xxxxxx-Foo"? Sure would stop a lot of 
confusion and you wouldn't need to be asking the question.


Kenn
LBNL

On 2/29/2008 10:14 AM, Joe Casadonte wrote:
> Assume:
> 
> * Ticket #1 is in the Queue Q1
> * Custom Field #1, named Foo, applies to all queues
> * Foo's value for Ticket #1 is 'Global'
> 
> A query results listing that includes CustomField.{Foo} will properly 
> show 'Global' for the value of Foo.
> 
> 
> Change the assumptions:
> 
> * Ticket #1 is in the Queue Q1
> * Custom Field #1, named Foo, applies only to Q1
> * Foo's value for Ticket #1 is 'Specific'
> 
> A query results listing that includes CustomField.{Foo} will properly 
> show 'Specific' for the value of Foo.
> 
> 
> Now, change the assumptions once more:
> 
> * Ticket #1 is in the Queue Q1
> * Custom Field #1, named Foo, applies to all queues
> * Custom Field #2, also named Foo, applies only to Q1
> * Foo's (#1) value for Ticket #1 is 'Global'
> * Foo's (#2) value for Ticket #1 is 'Specific'
> 
> A query results listing that includes CustomField.{Foo} will show 
> 'Global' for the value of Foo.
> 
> 
> Where is it determined which CF value to show?  I'm obviously asking 
> because I want the queue-specific one shown, not the global one.  I'm 
> pretty comfortable roaming around the source, but once I get to the 
> query and query results level, I just kind of get lost.  I suspect much 
> of it happens in some non-RT module (DBI or DBIx::SearchBuilder?) but I 
> can't help thinking that the CustomField stuff is very RT-specific, and 
> so has to be handled somewhere inside of RT.
> 
> Thanks!
> 
>