Filter Issue Scope(AQL) for Assets object custom field not working correctly with the "OR" operator in Assets

Still need help?

The Atlassian Community is here for you.

Ask the community

 

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

  

Summary

The Filter Issue Scope(AQL) in the Assets object custom field does not work correctly with the "OR" operator and provides incorrect object search results.

Environment

Jira Service Management Assets

Diagnosis

Using the "OR" operator in the Filter Issue Scope(AQL) results in an incorrect number of objects returned by the Assets object custom field as it returns the objects from the other object types as well.

For example, the Filter Issue Scope(AQL) should only return objects from the "object type1" object type but it returns objects from different object types.

Cause

The Filter scope (AQL) & Filter issue scope (AQL) works in the "AND" operator. So, the filter configuration is read in conjunction with the "AND" operator with the Filter scope, which results in an incorrect object search.

Solution

Adding a bracket to the Filter issue scope (AQL) to treat it as one query solves this issue.

For reference, now the result shows objects from the correct object type i.e. "object type1".







Last modified on Aug 23, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.