Perforce Job Field is Blank when Viewing an Issue
Symptoms
When viewing an issue in JIRA, you'll notice the Perforce Job is blank when viewing an issue.
Also, the following error is generated in the JIRA logs:
2009-05-06 17:16:28,296 http-8080-Processor23 ERROR [webwork.util.ServletValueStack] METHOD: "customFieldHtml", exception:
java.lang.NullPointerException
at com.atlassian.jira.ext.fisheye.perforce.PerforceConfigStoreImpl.getConfig(PerforceConfigStoreImpl.java:141)
at com.atlassian.jira.ext.fisheye.perforce.PerforceManagerImpl.jobExists(PerforceManagerImpl.java:209)
at com.atlassian.jira.ext.fisheye.perforce.PerforceManagerImpl.getOldJobs(PerforceManagerImpl.java:200)
at com.atlassian.jira.ext.fisheye.perforce.customfields.JobSwitchCFType.getVelocityParameters(JobSwitchCFType.java:110)
at com.atlassian.jira.issue.customfields.CustomFieldUtils.buildParams(CustomFieldUtils.java:433)
at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptor.getViewHtmlByValue(CustomFieldTypeModuleDescriptor.java:172)
at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptor.getViewHtml(CustomFieldTypeModuleDescriptor.java:148)
at com.atlassian.jira.issue.fields.CustomFieldImpl.getViewHtml(CustomFieldImpl.java:819)
at com.atlassian.jira.web.action.issue.ViewIssue.getCustomFieldHtml(ViewIssue.java:835)
Cause
The Fisheye Perforce plugin is trying to lookup old issue keys in the issue's change history and is failing. This can happen when you move one issue from one project to another. This is a known bug in the Fisheye Perforce Plugin. See FISH-293.
Resolution
This issue is fixed in version 2.5.2 of the Fisheye plugin. Please ensure that this version is compatible with your JIRA version in the Fisheye plugin installation guide.
Last modified on Jul 31, 2018
Powered by Confluence and Scroll Viewport.