Issue Summary

In the Old Transition experience, setting a workflow validator on the Parent field is not picking up the Parent field properly.

Note: This is reproducible in the Old Transition Experience only

Steps to Reproduce

• Configure a workflow transition with the workflow validator that checks if Parent field is not empty
  • In the same transition, add transition screen that includes the Parent field.
• If the Parent field is not in the transition screen, the validator works (it can see if the parent field is filled up)
• If the Parent field is in the transition screen, the validator keeps saying the Parent field is empty.
• If there is no transition screen, the validator can read the Parent field.

Expected Results

The validator should recognise the updated Parent value provided on the transition screen and allow the transition to proceed.

Actual Results

The validator continues to block the transition regardless of whether the Parent field is filled up before the transition, or whether it has been updated in the transition screen.

Workaround

Several options:

• Remove the transition screen for that workflow transition.
• Remove the Parent field from the transition screen for that workflow transition. Instruct users to update the Parent field directly on the issue view page before initiating the transition.
  The validator should recognise the updated Parent value provided on the transition screen and allow the transition to proceed.
• Create a support ticket to move over to modernized transition will also resolve this behaviour as the fix has been deployed there. JRACLOUD-99266: Native "Field Required" validator fails to recognise updates (clearing field) following the enablement of the Modern Transition Screen Experience
• For validators that check if a field is empty: Optional workaround is to use Matches regular expression for the validator, and use below REGEX for the field. This is the exact same behaviour as choosing the Isn't empty validator.

  .*+