Issue with setting Custom Statuses, Added statuses do not see any other statuses

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.
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’.
I have included a line below that contains the section of my site config that shows the Lifecycle. I am running RT 4.2.9
http://pastebin.com/0FfyXqgy
Any help with the matter would be great.
Thank you.Ashley EtheringtonAmsys Aftermarket Services

Hi Ashley,

Configuration questions are best sent to rt-users. [Done]

Comments inline.

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