Log files contain error messages requesting manual upgrades to workflow configuration

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

Symptoms

The following error appears in the logs:

1 2 3 4 5 6 Detected reference to Create Job Post-Function in filesystem-configured workflow 'blahblah' for transition 'rhubarb'. Please manually upgrade the configuration for this workflow by updating the post-function <arg name="class.name" /> elements containing 'com.atlassian.jira.plugin.ext.perforce.workflow.CreateJobFunction' to the new namespace: 'com.atlassian.jirafisheyeplugin.perforce.workflow.CreateJobFunction'.

Cause

The upgrade task for upgrading Perforce plugin workflows to Fisheye-JIRA plugin 2.0 workflows cannot automatically upgrade workflows loaded from file system xml descriptors at runtime.

Resolution

Upgrade the workflows manually by locating your JIRA workflow xml files in your JIRA webapp and updating the following elements:

1 2 3 4 5 6 7 8 9 ... <post-functions> ... <function type="class"> <arg name="class.name">com.atlassian.jira.plugin.ext.perforce.workflow.CreateJobFunction</arg> </function> ... </post-functions>

to:

1 2 3 4 5 6 7 8 9 ... <post-functions> ... <function type="class"> <arg name="class.name">com.atlassian.jirafisheyeplugin.perforce.workflow.CreateJobFunction</arg> </function> ... </post-functions>
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.