-
Bug
-
Resolution: Duplicate
-
Low
-
10.3.2, 10.3.4, 10.5.0, 10.3.6
-
6
-
Severity 2 - Major
-
10
-
Issue Summary
JQL Basic Search is not taking the Assets customfield value with Placeholder
Steps to Reproduce
- Login to Jira and create an Object Schema
- Create 2 Object Type: 'Country' and 'Users' with attribute 'attribute' mapped to Object Type Country
- Create multiple object in both Object Type and map the attribute 'Country' in 'Users' object type
- Create 2 customfield: Country_assets and Customer with below configuration
- Add both customfield to a Project Screen
- Create a Ticket with the details
- Navigate to Issue --> Search Issues
- Select Basic Search and look for the 'Customer' customfield and try selecting the objects from the drop-down
Expected Results
Object from the Drop-down are selected successfully
Actual Results
We get an error as mentioned in the screenshot but JQL is updated the value.
Recording here:
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
- duplicates
-
JSDSERVER-16138 Jira Issue Navigator Basic search allow filtering for impossible values for Assets custom fields not respecting the Filter Issue Scope/Filter Assign Scope
-
- Closed
-
- links to