Select CF does not change defaults in muti-context case

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.'

1 answer

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

736 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you