Issue Summary

When an attribute is missing for objectType, AQL should yield an empty list rather than generating an error.

Steps to Reproduce

• Create a schema and object type as follows
• In the given scenario, an object named “Geography” is created within the “Class” objectType. This object possesses two distinct attributes: “People Type” - designated for use as a placeholder, and “People” - configured with the ‘Filter by ALQ’ setting enabled as shown below.

objectType = ${People Type} AND "Entrance Card Type" = "Multi use" 

• The parent object type People comprises three distinct child object types:
  Students - This object type does not possess the Entrance Card Type attribute.
  Teachers - This object type includes the Entrance Card Type attribute.
  Guests - This object type also includes the Entrance Card Type attribute.

• When attempting to edit or create an object of type “Class“ and subsequently setting the “People Type” to “Students” while trying to select “People”, an error is encountered.
  

“The Jira server was contacted but has returned an error response. We are unsure of the result of this operation.”

• You can also test AQL directly:

objectType = Students AND "Entrance Card Type" = "Multi use" 

We will get error:

No matching attribute for AQL clause ("Entrance Card Type" = "Multi use")

Expected Results

As In previous versions (Jira 9.x), when the objectType attribute was missing, it returned an empty list instead of an error.

Below is an example of the practical use case of AQL used.

(objectType = ${People Type} and objectType = "Teachers" and "Entrance Card Type" = "Multi use") or (objectType in objectTypeAndChildren(${People Type}) and objectType in objectTypeAndChildren("Students"))

The functionality was as follows in Jira 9.x:

Selecting "Teachers" should yield only those entries where the attribute "Entrance Card Type" is set to "Multi use". Selecting "Students" should return all student entries.

Currently, the system consistently returns an error. If an attribute is absent for a given objectType, AQL should return an empty list rather than an error.

Actual Results

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

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: