Issue Summary
Error "Could not find Assets object/s!" is displayed when a group picker field containing multiple groups is used in a filter issue scope AQL.
Steps to Reproduce
- Create a new project.
- Create a new schema.
- Create an object type called "Product"
- Add attributes "Business Process" (Project type), "Ticket Process" (Default type, Select value), "State" (Status type)
- Create an object type called "Category"
- Add attributes "Business Process" (Project), "Business Ticket" (Default, Select), "Product" (Object, Product), "Groups" (Group type)
- Create test objects.
- Add an Assets Custom field called "Category"
- Associate it with the schema.
- Use filter scope "objectType = Category"
- Use filter scope AQL "State = Active AND "Business Process" = currentProject() AND "Ticket Process" in ${issuetype.label} and "Groups" in (${customfield_<id>.name${0}}) AND Product in (${customfield_<id>.label${0}})"
- Add an Assets Custom field called "Product"
- Associate it with the schema.
- Use filter scope "objectType = Product"
- Use filter scope AQL "State = Active AND "Business Process" = currentProject() AND "Ticket Process" in ${issuetype.label}"
- Add a group picker field (multiple groups) called "Groups"
- Create an issue in the test project, add the objects, and add two or more groups to the "Groups" custom field
Expected Results
The issue is created successfully.
Actual Results
Error "Could not find Assets object/s!" is displayed.
Workaround
Add dark feature assets.aql.scope.filtering.on.issue.update.disabled to the affected instance.
Versions Tested
| Testing Requirements |
Version |
Affected Version |
| Customers Reported Version |
10.3.2 |
Yes |
| Most Recent Bug-Fix Release |
10.3.5 |
Yes |
| Previous Major Release |
|
|
| Most Recent LTS |
|
|
| Previous Supported LTS |
|
|
| Other Versions.. |
10.3.4 |
Yes |
Bug
Low
