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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted 6 hours ago in Jira

We want to know what Jira Service Desk apps you're using!

Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...

25 views 0 4
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