More than one old Create Job post-function was defined for workflow transition error in logs

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 More than one old Create Job post-function was defined for workflow transition 'rhubarb' - they will be merged into ONE post-function under the new namespace.

Cause

This means that, pre-upgrade, you had more than one Create Job post-function configured for a particular workflow transition. This is typically redundant, so the upgrade process automatically merges them into one (which is placed in the position of the first Create Job post-function encountered).

Resolution

If you really wanted two instances of the Create Job post-function (ie. you have custom code that relies on it - two instances will not generally create two jobs) you can still manually add it after the initial upgrade. The upgrade process will not attempt to merge instances of the new version of the post-function.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.