-
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
-
-
- Closed
-
- links to
[JSDSERVER-16111] JQL Basic Search is not taking the Assets customfield value with Placeholder
| Fix Version/s | New: 10.3.8 [ 112691 ] |
| Assignee | New: Benjamin Suess [ c8bcca445054 ] |
| Description |
Original:
h3. Issue Summary
JQL Basic Search is not taking the Assets customfield value with Placeholder h3. 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 h3. Expected Results Object from the Drop-down are selected successfully h3. Actual Results We get an error as mentioned in the screenshot but JQL is updated the value. Recording here: h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
JQL Basic Search is not taking the Assets customfield value with Placeholder h3. 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 h3. Expected Results Object from the Drop-down are selected successfully h3. Actual Results We get an error as mentioned in the screenshot but JQL is updated the value. Recording here: h3. 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 [ |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Short Term Backlog [ 12074 ] | New: Closed [ 6 ] |
| Support reference count | Original: 5 | New: 6 |
| UIS | Original: 9 | New: 10 |
| Status | Original: Gathering Impact [ 12072 ] | New: Short Term Backlog [ 12074 ] |
| Symptom Severity | Original: Severity 3 - Minor [ 15832 ] | New: Severity 2 - Major [ 15831 ] |
Hi everyone,
This is Ben from the JSM team
This bug will be closed as it is a duplicate of of this bug https://jira.atlassian.com/browse/JSDSERVER-16138
This was only fixed on JSM 10.6, but will now be fixed on JSM 10.3 as well.
But in the mean time, please use the workaround of disabling the dark feature by