Unable to create perforce job with JIRA Fisheye plugin with error: Required parameter 'xxxx' not set!
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Unable to create a Perforce job from JIRA using the JIRA Fisheye Plugin (https://ecosystem.atlassian.net/wiki/display/FISH/JIRA+Fisheye+Plugin+3.0.17+-+Perforce+Job+Integration)
The following appears in the atlassian-jira.log
2016-02-27 07:30:57,536 http-nio-80-exec-14 ERROR polterageist 450x62483x1 18xm1c9 192.168.1.181 /secure/AjaxIssueAction.jspa [c.a.j.perforce.listener.JobUpdateListener] Could not commit job: Job: ISSUEKEY-123
User: polterageist
Description:
Test job for testing perforce integration
com.perforce.api.CommitException
at com.perforce.api.Job.commit(Job.java:365)
at com.atlassian.jirafisheyeplugin.perforce.listener.JobUpdateListener.createJob(JobUpdateListener.java:42)
...
Caused by: java.io.IOException: error: Operation 'dm-UpdateJobSpec' failed.error: Required parameter 'data' not set!
at com.perforce.api.P4Process.closeProcess(P4Process.java:587)
at com.perforce.api.Job.commit(Job.java:361)
... 246 moreCause
- There is a required Perforce job field configured in jobspec, which isn't mapped to any JIRA custom fields.
- The JIRA issue was submitted with option to create Perforce job, but no value was entered for the custom field mapped to a required Perforce Job field
Resolution
- Map a custom field in JIRA to the required Perforce job field, from the 'Map Custom Fields' link from the 'Perforce Job Integration' page.
- If the Perforce job field is not really required then edit your Perforce jobspec to remove or make the Perforce job field optional.
Last modified on Nov 7, 2018
Powered by Confluence and Scroll Viewport.