OCPBUGS-84710: Fix ConsoleDataView filter order: Name and Label should appear first

[rhamilto]

Fixes the ConsoleDataView filter toolbar ordering so that Name and Label filters appear first, before additional filters like Status, Roles, and Architecture.

What this PR does / why we need it

The ConsoleDataView component was displaying filter controls in an inconsistent order. When additionalFilterNodes were provided, they appeared before the standard Name and Label filters. This created a poor user experience as the most commonly used filters should always be first.

Which Jira issue(s) this PR fixes

Fixes: https://issues.redhat.com/browse/OCPBUGS-84710

Before

Filter toolbar displays: Status | Roles | Architecture | Machine set | MachineConfigPool | Name | Label

After

Filter toolbar displays: Name | Label | Status | Roles | Architecture | Machine set | MachineConfigPool

How to test this PR

1. Navigate to the Nodes list page (Compute > Nodes)
2. Observe the filter toolbar above the data table
3. Verify Name and Label filters appear first from left to right

Screenshots/recordings

See Jira: https://drive.google.com/file/d/1JDWL68H6iqL8qpxijNLIQyHqI1O7gwLA/view?usp=sharing

Summary by CodeRabbit

• Style
  • Adjusted the ordering of base filter elements in the data view for improved usability.

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-84710, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

Fixes the ConsoleDataView filter toolbar ordering so that Name and Label filters appear first, before additional filters like Status, Roles, and Architecture.

What this PR does / why we need it

The ConsoleDataView component was displaying filter controls in an inconsistent order. When additionalFilterNodes were provided, they appeared before the standard Name and Label filters. This created a poor user experience as the most commonly used filters should always be first.

Which Jira issue(s) this PR fixes

Fixes: https://issues.redhat.com/browse/OCPBUGS-84710

Before

Filter toolbar displays: Status | Roles | Architecture | Machine set | MachineConfigPool | Name | Label

After

Filter toolbar displays: Name | Label | Status | Roles | Architecture | Machine set | MachineConfigPool

How to test this PR

1. Navigate to the Nodes list page (Compute > Nodes)
2. Observe the filter toolbar above the data table
3. Verify Name and Label filters appear first from left to right

Screenshots/recordings

See Jira: https://drive.google.com/file/d/1JDWL68H6iqL8qpxijNLIQyHqI1O7gwLA/view?usp=sharing

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.

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-84710, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Fixes the ConsoleDataView filter toolbar ordering so that Name and Label filters appear first, before additional filters like Status, Roles, and Architecture.

What this PR does / why we need it

The ConsoleDataView component was displaying filter controls in an inconsistent order. When additionalFilterNodes were provided, they appeared before the standard Name and Label filters. This created a poor user experience as the most commonly used filters should always be first.

Which Jira issue(s) this PR fixes

Fixes: https://issues.redhat.com/browse/OCPBUGS-84710

Before

Filter toolbar displays: Status | Roles | Architecture | Machine set | MachineConfigPool | Name | Label

After

Filter toolbar displays: Name | Label | Status | Roles | Architecture | Machine set | MachineConfigPool

How to test this PR

1. Navigate to the Nodes list page (Compute > Nodes)
2. Observe the filter toolbar above the data table
3. Verify Name and Label filters appear first from left to right

Screenshots/recordings

See Jira: https://drive.google.com/file/d/1JDWL68H6iqL8qpxijNLIQyHqI1O7gwLA/view?usp=sharing

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]

📝 Walkthrough

Walkthrough

The filter node composition in a data view component was reordered so that base "Name/Label" filters render before additional filter nodes, rather than after them. No functional or control flow changes.

Changes

Cohort / File(s)	Summary
Filter Node Composition frontend/packages/console-app/src/components/data-view/ConsoleDataView.tsx	Reordered filter node rendering to display base "Name/Label" filters before additionalFilterNodes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing the filter order so Name and Label appear first in ConsoleDataView.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR modifies React component for filter reordering; no Ginkgo test files are modified with dynamic test names.
Test Structure And Quality	✅ Passed	The custom check for Ginkgo test code quality is not applicable to this PR, which only modifies a TypeScript/React component without adding or modifying any Go test files.
Microshift Test Compatibility	✅ Passed	PR modifies only a frontend React/TypeScript component file and does not add any Ginkgo e2e tests.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR modifies only ConsoleDataView.tsx, a TypeScript/React component, with no new Ginkgo e2e tests added, so the SNO test compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Frontend React component reordering filter elements with no impact on Kubernetes topology-aware scheduling.
Ote Binary Stdout Contract	✅ Passed	This PR modifies a frontend React/TypeScript component (ConsoleDataView.tsx) that handles UI filter ordering. It does not involve any Go test binaries, test infrastructure, or stdout operations covered by the OTE Binary Stdout Contract check.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only React/TypeScript UI components with no Ginkgo e2e tests added, making the check inapplicable.
Description check	✅ Passed	The PR description is well-structured and covers all essential sections including analysis, solution, before/after comparison, test instructions, and a Jira reference with proper formatting.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[TheRealJon]

/lgtm

[logonoff]

/lgtm

[logonoff]

/verified by screenshot

[openshift-ci-robot]

@logonoff: This PR has been marked as verified by screenshot.

Details

In response to this:

/verified by screenshot

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.

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 335d6bd and 2 for PR HEAD 91e2b4f in total

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD d21ae19 and 1 for PR HEAD 91e2b4f in total

[rhamilto]

@logonoff, I had to push integration test fixes. PTAL.

[logonoff]

/lgtm

[logonoff]

/verified by screenshot,ci

[openshift-ci-robot]

@logonoff: This PR has been marked as verified by screenshot,ci.

Details

In response to this:

/verified by screenshot,ci

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, rhamilto, TheRealJon

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 [TheRealJon,logonoff,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.

[openshift-ci-robot]

@rhamilto: Jira Issue Verification Checks: Jira Issue OCPBUGS-84710
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-84710 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Fixes the ConsoleDataView filter toolbar ordering so that Name and Label filters appear first, before additional filters like Status, Roles, and Architecture.

What this PR does / why we need it

The ConsoleDataView component was displaying filter controls in an inconsistent order. When additionalFilterNodes were provided, they appeared before the standard Name and Label filters. This created a poor user experience as the most commonly used filters should always be first.

Which Jira issue(s) this PR fixes

Fixes: https://issues.redhat.com/browse/OCPBUGS-84710

Before

Filter toolbar displays: Status | Roles | Architecture | Machine set | MachineConfigPool | Name | Label

After

Filter toolbar displays: Name | Label | Status | Roles | Architecture | Machine set | MachineConfigPool

How to test this PR

1. Navigate to the Nodes list page (Compute > Nodes)
2. Observe the filter toolbar above the data table
3. Verify Name and Label filters appear first from left to right

Screenshots/recordings

See Jira: https://drive.google.com/file/d/1JDWL68H6iqL8qpxijNLIQyHqI1O7gwLA/view?usp=sharing

Summary by CodeRabbit

• Style
• Adjusted the ordering of base filter elements in the data view for improved usability.

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.

[rhamilto]

/cherry-pick release-4.22 release-4.21

[openshift-cherrypick-robot]

@rhamilto: new pull request created: #16383

Details

In response to this:

/cherry-pick release-4.22 release-4.21

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.

[openshift-merge-robot]

Fix included in release 5.0.0-0.nightly-2026-05-01-010944