-
Bug
-
Resolution: Fixed
-
Low
-
24
-
Severity 3 - Minor
-
3
-
Summary
AQL with a user type attribute does not work due to the case sensitivity of another attribute with the same name
Steps to Reproduce
- Create an "owner" user type attribute in object type1
- Create an "Owner" user type attribute in another object type2
- Select one of the Jira users, eg: "lily" on a few objects in both the object types
- Try to execute an IQL using the user type attribute on both of these object types:
"owner" = "lily" on objecttype1 "Owner" = "lily" on objecttype2
Expected Results
AQL returns the results
Actual Results
Both the IQL returns results for object type2:
But none of the IQL's work for object type1
Even if you try to use the Basic search, the "owner" attribute" will not appear as a user type attribute in object type1, while it does in the object type2:
Workaround
If you are using the same names for attributes across object types, make sure their case sensitivity matches.
In this case, updating the "Owner" attribute to "owner" in objecttype2 solved the issue.
- duplicates
-
-
- Closed
-
[JSDCLOUD-10231] AQL with an attribute does not work due to case sensitivity of another attribute with same name
This cant be considered as low priority... Premium cloud customers are working with thousands of objects and thousands of different object types and attributes... Severals teams can managed the same object schema and create object type with the same attributes. It's sometimes impossible to guarantee that they won't use the same attributes names.
Welcome to the real world of using Atlassian products !
Please consider this bug as major at least... It's affecting Premium and Enterprise customers with a large number of data in Assets.
Hi everyone,
This is Radu from the Assets team. This bug is fixed and I confirmed the functionality to be working as expected.
I've replicated the steps and confirmed that AQL retrieves the correct objects regardless of case used for the attributes. E.g. "Owner = lilly" and "owner = lily" return results on both object types.
Sincerely,
Radu Apostoleanu