Issue Summary

Note- This is related to Bug JSDSERVER-15141 . It looks like the issue is fixed in the "Edit Issue" screen. However, the issue still exists for inline Edit of the Assets custom field on the Issue View screen.

Issue Summary-

Assets object cannot be added to an Assets custom field with error "Could not find Assets object/s". This seems to be affecting only when the Filter Issue Scope and/or Filter Assign Scope has AQL involving placeholder like currentReporter(), ${assignee}, ${reporter}.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create an ITSM Project.
2. Create sample data in Assets with Object Schema, Object Type and some Objects with "User" attributes.
   
   1. Below we have one of the attribute "Username" of type "User" 
      
3. Create an Assets object custom field and add it to the all the screens of the new project.
4. Configure the custom field to get objects from the new schema as below
   
5. Create a new issue and select the required object in the "Asset User Field" custom field based on the Reporter.
   
6. The new issue is created fine.
   
7. Now, change the Reporter to some other user and try to inline Edit the "Asset User Field" custom field value based on the new Reporter.
   The Error "Could not find Assets object/s" is Observed
   

We are able to update the "Asset User Field" fine in the Edit Screen

• Go to the Edit Screen and update the "Asset User Field".{}
  
• Reload the page and the "Asset User Field" is updated on the Issue View screen.
  

Expected Results

The inline edit to update the asset custom field on the issue view screen should work without Errors.

Actual Results

The inline edit to update the asset custom field on the issue view screen results in Error "Could not find Assets object/s"

Workaround

• Workaround 1:

  You can go to the Edit screen and update the custom field value.

• Workaround 2 :

Please add 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.