• Type: Bug
• Resolution: Duplicate
• Priority: Low
• Fix Version/s: 10.3.8
• Affects Version/s: 10.3.2, 10.3.4, 10.5.0, 10.3.6
• Component/s: Assets - Jira Field & JQL
• Labels:

  • ril

1. Country_assets-customfield-confi.png

   17/Mar/2025 1:59 PM

   168 kB

   Shreekesh Mohan

2. CoUNTRY-customfield-confi.png

   17/Mar/2025 1:59 PM

   167 kB

   Shreekesh Mohan

3. Country-object.png

   17/Mar/2025 1:59 PM

   196 kB

   Shreekesh Mohan

4. Screen Recording 2025-03-14 at 7.00.37 PM.mov

   17/Mar/2025 1:59 PM

   32.93 MB

   Shreekesh Mohan

[JSDSERVER-16111] JQL Basic Search is not taking the Assets customfield value with Placeholder

Benjamin Suess made changes - 29/May/2025 4:55 AM

Fix Version/s

New: 10.3.8 [ 112691 ]

Benjamin Suess made changes - 29/May/2025 4:33 AM

Assignee

New: Benjamin Suess [ c8bcca445054 ]

Benjamin Suess made changes - 29/May/2025 4:33 AM

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 [JSDSERVER-15453|https://jira.atlassian.com/browse/JSDSERVER-15453]

Benjamin Suess made changes - 29/May/2025 4:33 AM

Link

New: This issue duplicates JSDSERVER-16138 [ JSDSERVER-16138 ]

Benjamin Suess made changes - 29/May/2025 4:32 AM

Resolution		New: Duplicate [ 3 ]
Status	Original: Short Term Backlog [ 12074 ]	New: Closed [ 6 ]

SET Analytics Bot made changes - 28/May/2025 4:05 AM

Support reference count

Original: 5

New: 6

SET Analytics Bot made changes - 28/May/2025 2:19 AM

UIS

Original: 9

New: 10

Marc Dacanay made changes - 28/May/2025 12:34 AM

Status

Original: Gathering Impact [ 12072 ]

New: Short Term Backlog [ 12074 ]

Navneeth S made changes - 26/May/2025 4:24 PM

Symptom Severity

Original: Severity 3 - Minor [ 15832 ]

New: Severity 2 - Major [ 15831 ]

Navneeth S made changes - 26/May/2025 4:20 AM

Affects Version/s

New: 10.3.6 [ 111290 ]

Load more older history items