Issue Summary

If a Jira ticket has an "Asset custom field" with at least one object not respecting the Asset custom field "filter scope", then, if any Jira issue fields (eg- label, component, summary etc) are edited in the "Edit Issue" screen, Error like below is returned

"Could not find Assets object/s <KEY>"

Steps to Reproduce

1. Create a New JSM Project
2. Create a New Object Schema, Object Type and few objects like below
   
3. Create an "Asset Custom Field" with Filter Scope like below where we are filtering all the Object under "TestObjectType "with Status as "Active"
   
4. Go to the JSM project and create a Jira issue and select the respective Object in the Custom Field.
   
5. Now, update the select Object and change the status to "Inactive" so that the "Asset Custom Field" Filter Scope is not respected.
   
6. If we go back to the issue that was created above and update any field for example-summary on the issue, then Error "Could not find Assets object/s <KEY>" is seen
   

Note- This problem was not seen in JSM 5.12.x. Jira issue can be edited even if the selected object does not match the "Asset Custom Field" Filter Scope

Expected Results

Users should be able to edited Jira issue even if the Object present on the Asset Custom Field on the issue does not match the "Asset Custom Field" Filter Scope

Actual Results

Users is not able to edited Jira issue if the Object present on the Asset Custom Field on the issue does not match the "Asset Custom Field" Filter Scope. Error "Could not find Assets object/s <KEY>" is seen.

Workaround

Please disable the Feature flag : assets.aql.scope.filtering.on.issue.update.disabled in your environment. For details of how to update feature flag refer this page.

Note- With this feature flag added, the "Filter Issue scope" configuration on the asset custom field is not respected and you can type and select the Asset Objects from different Object Schema.

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: