States on Custom Tables (this is embarrassing)

[Uncle Rob]

So I have a custom task type with several states, 3 of which are considered "Closed".

Since all my workers and customers work off of Task lists, I opted to modify choices for Task.State rather than make a custom table based state.

Ok, so I created all my state choices and the three "Closed" ones have values of 50,60,70 respectively.   I did a dictionary override for my custom table and listed them in the close_states attributes (per this wiki page)

My problem is no matter which of the ending states I pick, the system interrupts and sets the State value to 3.  
Suspecting the "Task Active State Management" business rule was to blame, I deactivated it, and sure enough, I could pick whatever closure state I wanted unmolested.

My problem is, I can't figure out how or why Task Active State Management is determining that I want a default State of 3 on inactivation.

Anyone run into this kind of thing before?

[Brad Tilton]

That's a good question. I would lean toward it never making it in.

[Uncle Rob]

And you know what else is going to be awesome?   Attempting to work around Task Closer from a

[coryseering]

You'll want to track PRB602732. PRB572779 was closed as a duplicate of it.

[Uncle Rob]

Ah!   So this isn't a case of me just not knowing my craft?  

[coryseering]

Nope. Just good old problem management opacity.