Running advanced search for a field without a context results in error.

Issue Summary

If the context of a field is deleted, there is no way we can validate if that field has any value stored in any of the issues as the search returns error. This is problematic as if we need to delete the field, we cannot verify if field has any value in any issue or not.

Steps to Reproduce

1. Create a custom field of the type "text" and named "Test" (Note: This applies to all field types) 
2. Add this field to a project by adding to necessary screens. 
3. Add some value to this field.
4. Now delete the context for this field
5. Run a JQL to look for all values available for this field - "Test" is not empty

Expected Results

The query should be successful.

Actual Results

It errors out stating "Field does not exist or you do not have permission to view it"

Workaround

Create context for Test field again and now it will work. 

Where workaround May not work

If the custom field type contains options example - "Checkboxes", then even after adding a context we may face error. Adding to it, once the context is deleted, we cannot know what were original options available.