Issue Summary

When people use the new workflow editor, even a small change—such as moving a status on the diagram or adding a new status to the workflow—and then publishing it, affects the order of the post functions as shown in the old workflow editor.

We rely on a custom post function, for example:

“The field Requestor will take the value from Reporter.”

This post function is configured at the end of the list of post functions in the Create transition (position 5).

When a change is made using the new editor and published, the order of post functions is modified so that this post function is moved up between the first and second positions. This change in execution order affects the cloning operation. Because the order is altered, cloning the ticket fails and the customer sees errors such as:

We could not clone the ticket.

We couldn’t copy the value from Requestor to  Reporter.

This effectively breaks their cloning process after any edit done via the new workflow editor.

Steps to Reproduce

Reproduced on my own Jira Cloud instance with the old and new workflow editors:

1. In the old workflow editor, edit a workflow.

1. On the Create transition, add a new post function and place it at the end of the list using the old editor.

• • Example:

• • • The field Reporter will take the value from Assignee. Source and destination issue are the same.

1. Associate this workflow with any project if not already associated.

1. Open the same workflow in the new workflow editor.

1. Make a minimal change using the new editor, for example:

• • Move the position of any status in the diagram, or

• • Add a new status to the workflow.

1. Publish the workflow update from the new editor.

1. Go back to the old workflow editor.

1. Open the Create transition and check the Post functions section.

Expected Results

• Editing a workflow in the new workflow editor (including minor diagram adjustments or adding statuses) should not change the relative order of existing post functions as configured in the old editor, especially for custom post functions on the Create transition.

• Cloning should continue to work as before, and field-copy post functions should execute in the originally configured order.

Actual Results

• After publishing changes from the new workflow editor, the execution order of post functions on the Create transition is altered.

• A post function that was at the end of the list is moved earlier in the sequence (between first and second positions).

• This change in order breaks cloning operations that depend on that post function, resulting in errors such as:

• • We could not clone the ticket.

• • We couldn’t copy the value from Reporter to Super Epic Reporter.

Workaround

Move manually the position of the post function in the old editor