Select CF does not change defaults in muti-context case

[Tom Towkach]

I have a select, let's call it classy. Classy for A project has default of let's say "Very." Classy for B project defaults to "Not Very." When I create an issue in 5.1.2 and the project/issue type is already selected, my defaults show up as expected all the time for A&B; however, if you need to change from project A to project B, you would see select classy is not the default for that context. It's set to 'none.'

[Tom Towkach]

There is a JAC for this. And there is a work around. Ask me if you need it.