Version Picker (multiple versions) field gives nullpointerexception if context has IssueType as well as Project

Summary

Version Picker (multiple versions) field gives nullpointerexception on Issue Navigator as well as on "Edit Default Screen" if context has IssueType as well as Project

Environment

• Reproduced with JIRA 6.4.7

Steps to Reproduce

1. Add some versions for the project
2. Configure a custom field of type Version Picker (multiple versions)
3. Now, configure the context of the field to use some specific Projects as well as Issue types instead of Global context(see screenshot)
4. Run a re-index of JIRA
5. Create some issues with this field
6. Search for these issues on Issue Navigator or try to edit the default value of the custom field.

Expected Results

The issues show up properly.
The default value can be edited without any problem.

Actual Results

The below exception is thrown in the atlassian-jira.log file:

2015-07-14 13:04:12,587 ajp-8009-13 DEBUG aaaaa 784x74040x1 kan0la 192.168.100.36 /rest/issueNav/1/issueTable/stable [com.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'java.lang.NullPointerException - null'.
java.lang.NullPointerException
at com.atlassian.jira.issue.customfields.impl.VersionCFType.getUnreleasedVersionFirst(VersionCFType.java:288)
at com.atlassian.jira.issue.customfields.impl.VersionCFType.getVelocityParameters(VersionCFType.java:273)
at com.atlassian.jira.issue.customfields.CustomFieldUtils.buildParams(CustomFieldUtils.java:475)
at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.getViewHtmlByValue(CustomFieldTypeModuleDescriptorImpl.java:345)
at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.access$100(CustomFieldTypeModuleDescriptorImpl.java:46)

Workaround

The workaround is to switch to Global context and then re-index the instance.