Re: [rt-users] Can't resolve in-progress ticket?

2014-09-03 Thread Rezty Felty
:16 AM To: Alex Peters a...@peters.netmailto:a...@peters.net Cc: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: Re: [rt-users] Can't resolve in-progress ticket? Yes, we fixed it with lifecycle

Re: [rt-users] Can't resolve in-progress ticket?

2014-09-03 Thread Kevin Falcone
On Tue, Aug 26, 2014 at 02:16:28PM +, Rezty Felty wrote: Yes, we fixed it with lifecycle entries in the RT_SiteConfig.pm, I hadn’t realized that lifecycles had replaced status’. 4.0 used to warn, 4.2 doesn't warn anymore about 3.8 variables. However, it's documented in the upgrading docs.

Re: [rt-users] Can't resolve in-progress ticket?

2014-08-26 Thread Rezty Felty
To: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com Cc: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: Re: [rt-users] Can't resolve in-progress ticket? Sounds like a possible

[rt-users] Can't resolve in-progress ticket?

2014-08-25 Thread Rezty Felty
I just upgraded our RT system, from running on SLES 11 to RHEL 6.5, RT from 3.8.7 to 4.2.6, and mysql from an old version to the latest mariadb. Upgrade went smoothly, have tested everything, all seems to be well, except one thing. I have a ticket that a user placed in in-progress status

Re: [rt-users] Can't resolve in-progress ticket?

2014-08-25 Thread Rezty Felty
...@adknowledge.com Date: Monday, August 25, 2014 at 10:30 AM To: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: [rt-users] Can't resolve in-progress ticket? I just upgraded our RT system, from

Re: [rt-users] Can't resolve in-progress ticket?

2014-08-25 Thread Alex Peters
-users@lists.bestpractical.com Subject: [rt-users] Can't resolve in-progress ticket? I just upgraded our RT system, from running on SLES 11 to RHEL 6.5, RT from 3.8.7 to 4.2.6, and mysql from an old version to the latest mariadb. Upgrade went smoothly, have tested everything, all seems