Perforce Job got deleted immediately

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Summary

Symptoms

The following appears in the atlassian-jira.log:

1 2015-01-30 23:47:10,168 http-bio-xxx-exec-7 DEBUG admin 1427x1744x3 1pt7b76 xx.xx.xx.xx /secure/QuickCreateIssue.jspa [com.perforce.api.Debug] P4Process.exec: p4 -s -p xx.xx.xx.xx:xxxx -u xxxxx -c perforce job -d TEST-12

Diagnosis

Turn on the verbose debugging from Perforce Configuration page to check the perforce job logging.

Cause

If Hidden Job Switch field is not detected in the issue, the perforce job will be auto deleted.

Solution

Resolution

Associate the Hidden Job Switch field with the project issue.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.