Change Request - State changes to Numeric value

[snowuser111]

Hi Experts,

Can anyone help me please.
I have created new choices in drop down of Change 'State' like : Failed, Successfully Completed.
But when I select anyone example 'Failed' or 'Successfully Completed' ,
and save it next time when I open the change it shows me numeric value like 3 (i.e Closed Complete) in State instead of ( Failed or Successfully Completed) which was OOB.
I have removed them from -->personalise choices. Not sure why it is selecting state as 3 every time. I have to update it once again.
Where this OOB selection can be removed ?
Why it changes to numeric value? and the old one which was already present in default instance?

Thanks

[Fathah]

okay, but your attachment is successfully completed rght?
Please make the dependent value as 3 for closed complete then check.

[snowuser111]

I gave 22 as dependent value for the above . But still when the change state changes to (3) Closed Complete. Is it somewhere written in Client scripts or UI.... not sure...

[TJW2]

Something is setting the state to a 3, this is probably an OOB BR. When you start playing with the 'values' of the state field you must be very careful and verify what is effected. I would suggest keeping your 'Close Complete value of 3' and Changing the label to be 'Successfully Completed'.

[snowuser111]

Hi Terri,

Not every time the state should be 'Succesfully Completed'. It depends on the choice of the IT team to mark Change it as Failed / Succesfully Completed depending upon the implementation. But in my condition whichever I select either Failed/Succesfully Completed , after saving it changes back to "Closed Complete" (i.e 3)

Thanks

[TJW2]

There are OOB BRs that are getting in your way:

mark_closed (change_request table): This sets active to false
if (current.state > 2) {
current.active = false;
}

task closer: (task table): This one is setting your state to close when active changes to false.

You will need to take a look at these and all other OOB BRs that deal with states. Remember some of these are running on the 'task' level so will effect other tables.