Why was known error removed as a state on the problem record?

[Jason Page]

Why was known error removed as a state on the problem management workflow? It makes complete sense to be able to park records that have an unknown root cause in this state, attach the appropriate workaround/known Error KB article, and then one can return to the record if/when a permanent fix is found. Resolving problem records to rick acceptance makes teams have to open another problem record in the future if root cause is found and then tie another problem record to the known error KB article as well. Just like to understand ServiceNow's thinking in removing this critical state for a problem record from the workflow.

[bammar]

Do you know for sure if ServiceNow removed this?  If they did but noone finds this post, you may have to open a Case. 

Aside from that.... Depending on how many devs you have ive seen cases of inadvertant- hiding/relabling of options, misuse or not using Dictionary overrides, UI policy/ client scripts that would lead to an option dissapearing....

And transcending it all I love and beleieve in the power to control your servicenow destiny- so I take it the existing records still retain the value. In any case... if you find that it is from servicenow and locate what is responsible for hiding it and you want to reverse it- I think you should but knowing the how and why wont hurt. If what i said is really obvious and already been considered by you then disregard but i thought id answer.

[Jason Page]

I am pretty sure ServiceNow removed this state from the problem workflow.