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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,981 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot