[rt-users] FW: [rt-devel] Issue with setting Custom Statuses, Added statuses do not see any other statuses.

[Ashley Etherington]

After changing to the most recent script,  and resetting the Mason Cache this is now working perfectly.
Thank you for all the help.

From: migetismad at hotmail.com
To: rt-users at lists.bestpractical.com
Date: Thu, 9 Jul 2015 15:49:51 +0100
Subject: [rt-users] FW: [rt-devel] Issue with setting Custom Statuses, Added statuses do not see any other statuses.




Thank you for your response M
My perl is not great so I was unsure how/if I could put spaces in the Hash's key so I named them just a shorter variant of the status.  
the results in the following image http://prntscr.com/7qp9ra
So the statuses appear correctly (So maybe not a 25 character limit?)
Now if I try to set the status to a non-RT Default after submitting it shows this http://prntscr.com/7qpaz6
I just modified my code to something that did not throw any errors but I get the same result.  New code is here http://pastebin.com/a8HRz0sG
Once again,  Any help is greatly appreciated.
Thank you.Ashley Etherington.

> Date: Thu, 9 Jul 2015 09:17:11 -0500
> Subject: Re: [rt-devel] Issue with setting Custom Statuses, Added statuses do not see any other statuses.
> From: mzagrabe at d.umn.edu
> To: migetismad at hotmail.com; rt-users at lists.bestpractical.com
> 
> Hi Ashley,
> 
> Configuration questions are best sent to rt-users. [Done]
> 
> Comments inline.
> 
> On Thu, Jul 9, 2015 at 4:54 AM, Ashley Etherington
> <migetismad at hotmail.com> wrote:
> > Hi Everyone.
> >
> > We have decided that instead of using a Sub-Status custom field, that we
> > would add all of our statuses to the main built in RT Ticket status.  The
> > first initial pass appears to work but when we use one of the new statuses,
> > we are unable to select any other status.
> 
> Okay.
> 
> > For example if I set the status to 'Awaiting Parts' and submit the form,
> > The only status I can then set it to is 'Awaiting Status'.
> 
> A few comments.
> 
> 1) Start with the default lifecycle and make small changes to it. You
> should be able to find your issue.
> 
> 2) From what I can see in your "transitions" hash, there is no key of
> "Awaiting Parts". Thus there are no valid transitions for that status
> to change to. I'm not sure how "Awaiting Status" is showing up.
> 
> 3) I just read on rt-user that there is a 25 character limit for
> status names. If that is true, then you are running into that wall as
> well.
> 
> Cheers!
> 
> -m

 		 	   		   		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150709/a5a5897b/attachment.htm>