Issue Summary

When an AQL is entered for an Asset Object custom field's Filter Issue Scope or Filter Assign Scope , a change that is made that would cause the field's value to be no longer in scope does not reset the value of the field, even if that change happened at the time an issue was edited, within the issue that was being edited

Steps to Reproduce

1. Create a Sample IT dataset object schema - IT
2. Create two hosts, create two CPU's, then link a CPU to each host object
3. Create an Assets object custom field - Assets Parent
   1. Object Schema: IT
   2. Filter Scope: objectType = Host
4. Create an Assets referenced object custom field - Assets Reference
   1. Parent Custom Field: Assets Parent
   2. Reference direction: Outbound references
   3. Reference Type: CPU
5. Create an Assets object custom field - Assets Sub
   1. Object Schema: IT
   2. Filter Scope (AQL): objectType = CPU
   3. Filter Issue Scope (AQL) and Filter Assign Scope (AQL): object having inboundReferences(CPUs IN (${Assets Reference${0}}))
6. On a Jira Issue, edit:
   1. The Assets Parent to be Host1
   2. The Assets Reference to be CPU1
   3. The Assets Sub to CPU1
7. Save, and notice that the values are populated as per expectation. Edit the issue again and set:
   1. The Assets Parent to Host1

Expected Results

• The Assets Reference field has it's value reset
• The Assets Sub field has it's value reset

Actual Results

• The Assets Reference field has it's value reset
• The Assets Sub field does not have it's value reset

Even after saving the changes, the Assets Sub field is allowed to have the old (no longer valid to the AQL) value set.

Workaround

If only a single value is required (not require user selection from N choices), then you can force populate the field by choosing Make Filter Assign Strict checkbox

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: