[rt-users] RT v4.0 and ActiveStatus/InactiveStatus

[Kevin Falcone]

On Mon, Jun 13, 2011 at 02:10:56PM -0400, zbigniew at starpower.net wrote:
> Recently upgraded to 4.0 and getting these errors:
> 
> [Mon Jun 13 17:58:55 2011] [warning]: RT::ActiveStatus undefined, falling back to deprecated defaults (/opt/rt3/lib/RT/Queue_Overlay.pm:202)
> [Mon Jun 13 17:58:55 2011] [warning]: RT::InactiveStatus undefined, falling back to deprecated defaults (/opt/rt3/lib/RT/Queue_Overlay.pm:222)
> [Mon Jun 13 17:58:55 2011] [warning]: RT::InactiveStatus undefined, falling back to deprecated defaults (/opt/rt3/lib/RT/Queue_Overlay.pm:222)
> [Mon Jun 13 17:58:55 2011] [warning]: RT::ActiveStatus undefined, falling back to deprecated defaults (/opt/rt3/lib/RT/Queue_Overlay.pm:202)
> [Mon Jun 13 17:58:55 2011] [warning]: RT::InactiveStatus undefined, falling back to deprecated defaults (/opt/rt3/lib/RT/Queue_Overlay.pm:222)
> [Mon Jun 13 17:58:55 2011] [warning]: Deep recursion on subroutine "RT::Queue::SubjectTag" at /opt/rt3/lib/RT/System.pm line 232. (/opt/rt3/lib/RT/System.pm:232)

is /opt/rt3 your upgraded RT?

You appear to have left a lot of code around from 3.x
You skipped the part of docs/UPGRADING-4.0 which tells you that you
cannot just make upgrade into /opt/rt3 without lots of failures.

> Is this the correct way to add "research" to the status pulldown?

We'd need to see the full piece of code, and you also need to add
transition rules

> #Lifecyles
> 
> default => {
>         initial => ['new'],
>         active => ['open','research','stalled'],
>         inactive => ['resolved', 'rejected', 'deleted'],
> },
> 
> It's not showing up, I'm still seeing those errors, and it seems to me that config is missing something.
> 
> Would be wonderful to have a Wiki doc on the Lifecycles.   The RT_Config.pm isn't very detailed.

I find the RT_Config.pm Lifecycle documentation to be quite complete.
We updated it slightly to talk about rights in 4.0.1

Specific examples of things that can be updated would be useful.
I'd much prefer that enhanced Lifecycle documentation ship with RT, as
it is more likely to stay up to date.

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110613/4f98f4c9/attachment.sig>