[release-4.21] OCPBUGS-80931: Hide filter category selector when only one filter exists

[rhamilto]

Summary

Cherry-pick of OCPBUGS-78543 to release-4.21 branch. This improves UX by hiding the filter category dropdown selector when there's only one filter type available in ConsoleDataView.

Changes

• Added ConsoleDataView.scss with .co-console-data-view-single-filter class
• Applied class to DataView component when single filter is present
• Imported CSS utilities and stylesheet in ConsoleDataView.tsx
• Added Cypress test to verify category selector is hidden for both text and select filter types
• Added reusable test helper verifySingleFilterCategoryHidden
• Updated alertmanager receiver tests for consistency

The CSS uses !important to ensure the rule works across all breakpoints and targets the first child of the filter group (the category selector).

Test plan

• Verify filter category selector is hidden when only one filter exists
• Test with text-only filter (e.g., AlertmanagerConfig page)
• Test with select-only filter (e.g., Pod search page)
• Verify multiple filters still show the category selector
• Run Cypress tests to ensure new tests pass

🤖 Generated with Claude Code

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-80931, which is invalid:

• expected dependent Jira Issue OCPBUGS-78543 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Cherry-pick of OCPBUGS-78543 to release-4.21 branch. This improves UX by hiding the filter category dropdown selector when there's only one filter type available in ConsoleDataView.

Changes

• Added ConsoleDataView.scss with .co-console-data-view-single-filter class
• Applied class to DataView component when single filter is present
• Imported CSS utilities and stylesheet in ConsoleDataView.tsx
• Added Cypress test to verify category selector is hidden for both text and select filter types
• Added reusable test helper verifySingleFilterCategoryHidden
• Updated alertmanager receiver tests for consistency

The CSS uses !important to ensure the rule works across all breakpoints and targets the first child of the filter group (the category selector).

Test plan

• Verify filter category selector is hidden when only one filter exists
• Test with text-only filter (e.g., AlertmanagerConfig page)
• Test with select-only filter (e.g., Pod search page)
• Verify multiple filters still show the category selector
• Run Cypress tests to ensure new tests pass

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c2a47fc2-47bc-493f-8a2a-ce813cd7b26c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rhamilto]

/approve
/label backport-risk-assessed

[rhamilto]

/jira refresh

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-80931, which is invalid:

• expected dependent Jira Issue OCPBUGS-78543 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sg00dwin]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhamilto, sg00dwin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [rhamilto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@rhamilto: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.