Issue Summary

We configured an Assets field on a transition screen with a "Filter issue scope" AQL like this:

object HAVING outboundReferences("Name" IN (${issueType.label})) 

When the transition screen was displayed, changing the Issue Type dropdown dynamically updated the Assets field options without executing the transition. As of a few days ago, that dynamic update no longer works: the Assets field stays with options from the original Issue Type.

Steps to Reproduce

1.  Configure an Assets object type (called Type) and create two objects with the same name as two different Issue Types (Request and Incident)
2. Configure a second Assets object type (called Catalog) with an attribute Type that points to the object type created on step 1. Create two objects, each with a different Type.
3. Configure a transition screen with only the Issue Type field and one Assets object field.
4. Use Filter issue scope AQL of the Assets field with object HAVING outboundReferences("Name" IN (${issueType.label}))
5. In the UI, change the issue type before submitting the transition. Observe that the Assets field options do not query again or update.

Expected Results

When changing the Issue Type on the transition screen, the Assets field's available options should refresh instantly based on the updated issueType placeholder in the AQL.

Actual Results

The issue type placeholder is not re-evaluated live. The Assets dropdown remains unchanged until after the transition is executed or the page reloads.

Workaround

This is only happening on the new tranistion expirience, so you can disable the feature by going to :

Personal Settings -> Jira Labs -> New work transition experience