Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
My question is how did a particular field get in that state of Not configured for any context. From the creation screens it seems impossible to do so. I can go in and edit the configuration and I noticed that none of the issue types are selected or even the All issues selection. So, I think I can fix these but I'm wanting to know how they get this way?
I did see someone ask a question in Answers about whether it was safe to delete fields that showed Not configured for any context but no one had answered them
I've just been testing this here and I found out that this happens if you, for example:
JIRA will automatically remove this field from any contexts and remove the context if it doesn't have any other issue types in order to prevent any data corruption. Also, since the field is no longer associated with any issue types, it won't appear in any other screens even though it is configured in the Screens and Field Configurations.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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