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

This widget could not be displayed.

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
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

147 views 1 3
Join discussion

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