[rt-users] Query for custom fields using 'NOT LIKE' is no longer working

[Landon Stewart]

On Sep 7, 2016, at 5:01 AM, Keith Creasy <kcreasy at aph.org<mailto:kcreasy at aph.org>> wrote:

Hi everyone.

We are using RT 4.2.7. I think this used to work but now it isn’t. In a query like this:

Queue = 'Nimas' AND Priority > 49 AND (  Status = 'new' OR Status = 'open' OR Status = 'development' ) AND Due > 0 AND CF.{Type} NOT LIKE ‘Epic’

The “NOT LIKE” operator doesn’t work. I’ve tried it using the Query Builder and using Advanced. The “LIKE” operator does work. Does anyone have an idea for solving this?


I'm not sure if this means anything but on my screen the single quotes around the word Epic are different than the other words that have single quotes.

'development'
vs
‘Epic’

[cid:B1747A7F-2B3B-409D-9B0F-63C79811C7FC at telus]

--
Landon Stewart
Lead Analyst - Abuse and Security Management
INTERNAP ®
📧 lstewart at internap.com<mailto:lstewart at internap.com>
🌍 www.internap.com<http://www.internap.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20160907/6add14f6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-09-07 at 9.27.11 AM.png
Type: image/png
Size: 11013 bytes
Desc: Screen Shot 2016-09-07 at 9.27.11 AM.png
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20160907/6add14f6/attachment.png>