-
Bug
-
Resolution: Fixed
-
High
-
5.12.0, 10.3.2, 10.5.0
-
3
-
Severity 2 - Major
-
47
-
Issue Summary
Jira Issue Navigator Basic search allow filtering for impossible values for Assets custom fields not respecting the Filter Issue Scope/Filter Assign Scope
Steps to Reproduce
- Create an object schema and an object type in Assets
- Create an attribute of type status over the object type
- Create some objects with different statuses (ex. active/inactive)
- Create an Assets custom field and configure it to filter over the above object type
- Create some Jira issues with those objects
- Modify the custom field configuration and add as Filter Issue Scope or Assign Scope an AQL ex. status = active
- Go to the Jira Issue Navigator and in Basic Search filter the above custom field
- Observe that also the options (objects) that should not be filtered out are available even if the AQL in the custom field configuration deny them. # When try selecting them the *Could not find Assets object/s*is thrown out:
Expected Results
Those options/objects should not be offered for selection at all.
Actual Results
Those options/objects are shown and an error is thrown out.
Workaround
Disable the dark feature assets.aql.scope.filtering.on.issue.update by:
- Going to the page: <JIRA_BASE_URL>/secure/SiteDarkFeatures!default.jspa
- Adding assets.aql.scope.filtering.on.issue.update.disabled to the list of dark features
Note: This workaround will reintroduce JSDSERVER-15453
Versions Tested
| Testing Requirements | Version | Affected Version |
|---|---|---|
| Customers Reported Version | 10.3.2 | Yes |
| Most Recent LTS | 5.12.0 | No |
| Other version | 10.5.0 | Yes |
- is duplicated by
-
-
- Closed
-
- links to
