Thanks Alex, I had thought it was intermittent, but after some more troubleshooting it appears that the "intermittent" is the switch in context between the RT (works) and RTIR (does not) search pages (if searches are started from Search-->Tickets-->New Search) when it identifies the search against an RTIR queue. The issue happens consistently if I use RTIR-->Search-->New Search.
If I intercept the RTIR search request and append a "&Queue=Incident+Reports" to the form submission it does change the behaviour so after adding the entry you can search (with no results), and "Edit Search" returns the original error: [image: Inline image 2] You were spot on on the encoding - same behaviour on the page regardless of how the spaces are communicated (Confirmed it doesn't happen for custom fields without spaces in the name). Thanks, Rich On Thu, Mar 19, 2015 at 1:25 PM, Alex Vandiver <ale...@bestpractical.com> wrote: > On Thu, 19 Mar 2015 11:20:51 -0400 Richard Stevens > <piratef...@gmail.com> wrote: > > Hello, > > > > We recently upgrades to RT 4.2.10 / RT-IR-3.2.0 and I'm seeing > intermittent > > issues on search commands involving custom fields with spaces: > > [snip] > > The spaces are a red herring. The actual difference is that the > working one includes &Queue=Incident+Reports. Where is the latter > query being generated from? > - Alex >
