Summary

Strange and Confusing INFO messages about Custom Field contexts are thrown in JIRA logs, when you try to perform bulk change, if search filter is performed by specific project or issue type that a custom field's context is restricted to.

Steps to Reproduce

1. Create any custom field with a restricted context e.g. to specific project or issue types
2. Try to perform a bulk change with filter set to this specific project or issue type
3. Select from Issue Navigator Tools menu > Bulk Change > Choose Issues: select all Issues > Next > choose operation: select 'Edit Issues' > Next
4. No need to actually confirm the Bulk Change

Expected Results

There should be no INFO about missing configuration in the logs

Actual Results

INFO such as the following are thrown in JIRA logs, regarding custom fields that are restricted to the project or issue type in the search, right after selecting Edit Issues and clicking the next button.

2015-11-23 03:52:38,997 http-bio-8641-exec-6 INFO admin 232x1185x1 1cvxex3 127.0.0.1 /secure/views/bulkedit/BulkEditDetails.jspa [jira.issue.fields.CustomFieldImpl] No relevant config found for Story Points for the issue null
2015-11-23 03:52:39,010 http-bio-8641-exec-6 INFO admin 232x1185x1 1cvxex3 127.0.0.1 /secure/views/bulkedit/BulkEditDetails.jspa [jira.issue.fields.CustomFieldImpl] No relevant config found for myCustomfield for the issue null

Notes

1. This is more of an aesthetic bug actually - just a harmless INFO message, has no consequence whatsoever on the bulk change, which would still go on to execute successfully.
2. Modifying custom field contexts to global causes this weird INFOs to disappear.