[rt-users] Lifecycle statuses

[Max McGrath]

Hello -

I've been tasked with modifying the statuses we use in RT (we are running
RT 4.2.12).

I found the lifecycles document, but have a question regarding statuses.
I'm being asked to make statuses such as "Pending User", "Pending Vendor",
"Under Consideration", etc...

Is it wise to have a multi-word status.  In all the documents it appears
that every status is a single word (i.e., pending, considering,
processing).  Would it be wise to stick with a single word for my statuses?

Max
--
Max McGrath  
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu

Re: [rt-users] Lifecycle statuses

[Matt Zagrabelny]

On Mon, Jan 11, 2016 at 11:46 AM, Max McGrath  wrote:

> I was actually ready to move forward with the multi-word statuses until I
> got to the transitions area of the Lifecycle.  Would I just wrap a
> multi-word status is single quotes in the transitions area?
>
> Set( %Lifecycles, orders => {
> # ...,
> transitions => {
> ''  => [qw(pending processing declined)],
> pending => [qw(processing declined deleted)],
> processing  => [qw(pending declined delivery delivered deleted)],
> delivery=> [qw(pending delivered returned deleted)],
> delivered   => [qw(pending returned deleted)],
> returned=> [qw(pending delivery deleted)],
> deleted => [qw(pending processing delivered delivery 
> returned)],
> },
> # ...,
> });
>
>
The whole Lifecycles datastructure is just hash and array references. Here
is a contrived excerpt:

transitions => {
'really hungry' => [
'fatally starved',
'eating food',
],
'eating food' => [
'sleeping it off',
'having dessert',
],
},

-m

Re: [rt-users] Lifecycle statuses

[Matt Zagrabelny]

On Mon, Jan 11, 2016 at 11:22 AM, Max McGrath  wrote:

> Hello -
>
> I've been tasked with modifying the statuses we use in RT (we are running
> RT 4.2.12).
>
> I found the lifecycles document, but have a question regarding statuses.
> I'm being asked to make statuses such as "Pending User", "Pending Vendor",
> "Under Consideration", etc...
>
> Is it wise to have a multi-word status.  In all the documents it appears
> that every status is a single word (i.e., pending, considering,
> processing).  Would it be wise to stick with a single word for my statuses?
>

Use either single word or multi-word.

Benefits of single word:

1. Quick search is slick.
Find all of my tickets with status 'vendor' or 'new'

mzagrabe vendor new

2. Quicker to type things and you don't have to worry about people thinking
about spaces.

Benefits of multi-word:

The status will be (significantly?) more expressive and descriptive.

You will need to weigh those pros and cons against each other.

-m

Re: [rt-users] Lifecycle statuses

[Max McGrath]

I was actually ready to move forward with the multi-word statuses until I
got to the transitions area of the Lifecycle.  Would I just wrap a
multi-word status is single quotes in the transitions area?

Set( %Lifecycles, orders => {
# ...,
transitions => {
''  => [qw(pending processing declined)],
pending => [qw(processing declined deleted)],
processing  => [qw(pending declined delivery delivered deleted)],
delivery=> [qw(pending delivered returned deleted)],
delivered   => [qw(pending returned deleted)],
returned=> [qw(pending delivery deleted)],
deleted => [qw(pending processing delivered delivery returned)],
},
# ...,
});




--
Max McGrath  
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu

On Mon, Jan 11, 2016 at 11:42 AM, Matt Zagrabelny 
wrote:

>
>
> On Mon, Jan 11, 2016 at 11:22 AM, Max McGrath 
> wrote:
>
>> Hello -
>>
>> I've been tasked with modifying the statuses we use in RT (we are running
>> RT 4.2.12).
>>
>> I found the lifecycles document, but have a question regarding statuses.
>> I'm being asked to make statuses such as "Pending User", "Pending Vendor",
>> "Under Consideration", etc...
>>
>> Is it wise to have a multi-word status.  In all the documents it appears
>> that every status is a single word (i.e., pending, considering,
>> processing).  Would it be wise to stick with a single word for my statuses?
>>
>
> Use either single word or multi-word.
>
> Benefits of single word:
>
> 1. Quick search is slick.
> Find all of my tickets with status 'vendor' or 'new'
>
> mzagrabe vendor new
>
> 2. Quicker to type things and you don't have to worry about people
> thinking about spaces.
>
> Benefits of multi-word:
>
> The status will be (significantly?) more expressive and descriptive.
>
> You will need to weigh those pros and cons against each other.
>
> -m
>