[
https://issues.apache.org/jira/browse/ATLAS-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated ATLAS-5333:
-----------------------------------
Issue Type: Bug (was: Task)
> Atlas React UI: Clearing a Classification search filter triggers 400 Bad
> Request on empty parameters
> -----------------------------------------------------------------------------------------------------
>
> Key: ATLAS-5333
> URL: https://issues.apache.org/jira/browse/ATLAS-5333
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.5.0
> Reporter: Brijesh Bhalala
> Assignee: Brijesh Bhalala
> Priority: Major
> Labels: atlas-react
> Attachments: Screenshot from 2026-06-30 15-10-02.png
>
>
> When executing a Basic Search using only a Classification filter, clearing
> that classification filter via the "X" button causes the UI to fire an empty
> search request to the backend. The backend rejects this with a {{400 Bad
> Request}} error. This issue is isolated strictly to the Classification
> filter; clearing a Type (Entity) or Term (Glossary) filter correctly handles
> the empty state.
> *Steps to Reproduce:*
> This issue can be triggered via *two entry points* on the Dashboard:
> *Path 1 — Overview Card (Classifications link):*
> # Navigate to the Dashboard / Overview page.
> # Click on the {{Classifications}} count link inside the Overview card.
> # You are navigated to
> {{/#/search/searchResult?searchType=basic&tag=_ALL_CLASSIFICATION_TYPES&type=}}
> # Click the "X" on the {{Classification: _ALL_CLASSIFICATION_TYPES}} filter
> label.
> *Path 2 — "Classification Types In Use" Card:*
> # Navigate to the Dashboard / Overview page.
> # In the *"Classification Types In Use"* card, click on the *"X of Y
> classification types"* text link (e.g., {{{}"2 of 4 classification
> types"{}}}).
> # You are navigated to the Search Results page filtered by that
> classification.
> # Click the "X" on the active classification filter label to clear it.
> *Expected Behavior:* The UI should gracefully handle clearing the last active
> Classification filter exactly as it handles clearing a Type or Term filter —
> safely clearing results or preventing the API call from firing with entirely
> empty parameters.
> *Actual Behavior:* Clearing the Classification filter bypasses empty-state
> safety checks and fires a request with no parameters. The UI throws the
> following backend error:
>
> json
>
> {
> "errorCode": "ATLAS-400-00-047",
> "errorMessage": "No search parameter was found. One of the following MUST be
> specified in the request; typeName, classification, termName or queryText"
> }
> *Impact:* Inconsistent filter behavior across search entry points and a poor
> user experience, resulting in a raw JSON backend error being displayed to the
> user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
