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

On Sep 7, 2016, at 2:57 PM, Keith Creasy > wrote: Apologies. I keep forgetting that replies to this list go to the sender and not to the list… From: Keith Creasy Sent: Wednesday, September 7, 2016 5:55 PM To: 'Hien Ly'

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

Apologies. I keep forgetting that replies to this list go to the sender and not to the list… From: Keith Creasy Sent: Wednesday, September 7, 2016 5:55 PM To: 'Hien Ly' Subject: RE: [rt-users] Query for custom fields using 'NOT LIKE' is no longer working Hi. I think I

Re: [rt-users] Emails causing duplicate tickets?

That's the behavior I want. My problem is that the email then stays in the inbox or imap subfolder without being deleted. This causes RT to make a new ticket from that same email over and over again, since it always thinks it's a new message, even though it already processed it. On Wed, Sep 7,

Re: [rt-users] Problems with RT::ExternalAuth::LDAP After Upgrading to 4.4

> Which specific version of RT are you upgrading to? If you're upgrading > to 4.4.0, you'll need to be aware that a new config setting is required, > which doesn't appear in your config: > > Set($ExternalAuth, 1); > > In RT 4.4.1 we've removed the requirement to set this config. I am upgrading to

Re: [rt-users] Emails causing duplicate tickets?

On Sep 7, 2016, at 10:13 AM, Alex Hall > wrote: Hi all, I just ran into a very odd problem. I opened a ticket via email, which worked. But I then saw three more tickets open from that same email, each at the next mail polling. I haven't seen this

[rt-users] Emails causing duplicate tickets?

Hi all, I just ran into a very odd problem. I opened a ticket via email, which worked. But I then saw three more tickets open from that same email, each at the next mail polling. I haven't seen this problem before, and I don't know where to look to tell RT what to do with fetched emails. As I

Re: [rt-users] Problems with RT::ExternalAuth::LDAP After Upgrading to 4.4

> On Sep 7, 2016, at 12:13, Tim Gustafson wrote: > > Hi, Hi Tim, > I'm trying to upgrade my RT instance from 4.2 to 4.4. I use > RT::ExternalAuth::LDAP to authenticate users from my OpenLDAP server. > This configuration has been working perfectly in RT 4.2 (and earlier >

[rt-users] Problems with RT::ExternalAuth::LDAP After Upgrading to 4.4

Hi, I'm trying to upgrade my RT instance from 4.2 to 4.4. I use RT::ExternalAuth::LDAP to authenticate users from my OpenLDAP server. This configuration has been working perfectly in RT 4.2 (and earlier versions) for years. After upgrading to RT 4.4, I am not able to log in to RT at all. My

Re: [rt-users] Moving entire RT instance between two servers?

Hi Alex I recently shifted from physical server to VM. First I downloaded the RT source and ran the configure and make fixdeps to get all the required Perl modules on the target machine. (I also had some other modules I needed outside of core for extensions and custom code, had to get those by

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

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