Summary

The bug fix for JSDSERVER-12730 is effective for new issues created after the upgrade, but not for tickets created before the upgrade (and have entered the "approval" state).

Steps to Reproduce

Below is a simple test case that can be used to replicate this issue:

1. Create an object schema, an object type and add a User field to the object type:
   
2. Add 2 objects under the object type and select users for each object:
   
3. Create an Asset custom field that references the object type and associate it with screens:
   
4. Go to the default Change Management workflow for JSM and add approval to the first status "Peer review / change manager approval":
   
5. Select the asset custom field, related transitions and publish the workflow:
   
6. Create a Change request and try editing the Asset custom field:
   

Expected Results

The user shown in the Approvals will change accordingly when changing the Asset custom field.

Actual Results

• The user does not change in JSM 5.12.25. We know this is caused by the bug JSDSERVER-12730.
• After upgrading from JSM 5.12.25 to JSM 10.3.8, the issue no longer exists for new issues, but tickets created before the upgrade still have the JSM 5.12.25 behaviour.

Workaround

Workaround 2 (automatic transition) detailed in the bug JSDSERVER-12730 can be applied in JSM 10.3.8 for old issues.