Summary:

There is a inconsistency in how Jira Cloud handles workflow validation context. While standard field validators (like Assignee) correctly evaluate data entered on a transition screen, relational validators (like Parent Status) do not. 

For example - Currently for native Jira Cloud workflow validators (such as "Validate that parent work items are in a specific status") If a transition screen includes a field that is part of the validation logic (e.g., the Parent field), and a user updates that field on the screen to satisfy the validator, the validator continues to fail. 

Note: This is reproducible in the Old and New/Modern Transition Experience

Steps to Reproduce:

1. Configure a workflow transition with the native rule: "Validate that parent work items are in a specific status" (e.g., Parent must be "In Progress").
2. Add the Parent field to the transition screen for that transition.
3. Attempt to transition an issue whose current parent is in an invalid status (e.g., "To Do").
4. The validator correctly blocks the transition.
5. On the same transition screen, change the Parent field to a different issue that is already "In Progress".
6. Click the transition button again.

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, referencing the status of the original parent stored in the database.

Workaround

Remove the Parent field from the transition screen. Instruct users to update the Parent field directly on the issue view page before initiating the transition.