Hi,
after creating two custom fields with the same name and apply them to
two different queues I’ve encountered a problem with the ticket search
(wrong results).
Before digging deeper in this I want to ask if it is ok if custom fields
don’t have unique names or if custom fields should have unique names.
Chris
after creating two custom fields with the same name and apply them to
two different queues I’ve encountered a problem with the ticket search
(wrong results).Before digging deeper in this I want to ask if it is ok if custom fields
don’t have unique names or if custom fields should have unique names.
In general, this works, but I keep finding more and more corner cases
with it. In particular, if RT doesn’t have some Queue context to help
it out, hilarity ensues.
We’ve also fixed several bugs around this in newer versions, so
without knowing if you’re still looking at 3.8 or are on 4.0, the
behavior may be different.
-kevin
Hi,
after creating two custom fields with the same name and apply them to
two different queues I’ve encountered a problem with the ticket search
(wrong results).Before digging deeper in this I want to ask if it is ok if custom fields
don’t have unique names or if custom fields should have unique names.
Well, RTIR 2.6 and older use this for State and it works with RT 3.8, but
it’s better to avoid this. SQL for searches by such CFs gets more
complicated. Anyway, search bugs should be reported and fixed as it used
to work we are not planning to forbid such setups.
Chris
We’re hiring! Careers — Best Practical Solutions
Best regards, Ruslan.
Just reporting the current state of affairs for anyone stumbling into this thread.
It’s okay to have non-unique CF names, but this might lead to unexpected search results. In particular searches with negations will behave as if the second term wasn’t there: Queue=myqueue AND CF.{non-unique} NOT LIKE value. This is not a bug. The search correctly finds any customfield named non-unique that isn’t like value and adds the ticket to the results.
The correct way is to use CF IDs in searches. (or just avoid all this and use unique CF names)