Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Custom field global context not applying to all projects

I have a custom dropdown field with two contexts - one specific and one global. It's working correctly for the specific context, and for most of the projects that would fall under global, but there are several projects created recently that should be covered by the global context where the field is displaying, but there are no values.

Is there some other setting I may be missing? All of the projects where the values are missing were created with the "share settings with another project" property, and the project they're based on does display the values.

This is what the field configuration looks like; the default at the top is applying to about 20 projects correctly, and the OpexOnly is applying correctly to the two selected projects.




1 answer

1 accepted

0 votes
Answer accepted

This is strange, but it appears that the field is taking 10-12 seconds to load the values on the projects in question, but the values are there. 

I m facing similar issue where the contexts created for the custom field is disappering.. the earlier created ones where also missing suddenly.. no idea what is happening in Cloud JIRA

I am trying to create cascade field with a dozen contexts, why does it only allow the first one to be global? As I add the additional contexts it is requiring me to choose project(s) I want them to all be global for all issue types and projects.

I figured out what I was doing wrong, I only needed to create one context for my scenario. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events