Skip to content

[release-4.21] OCPBUGS-84967: Add bottom pagination to ConsoleDataView for mobile responsiveness#16396

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
rhamilto:OCPBUGS-84967
May 5, 2026
Merged

[release-4.21] OCPBUGS-84967: Add bottom pagination to ConsoleDataView for mobile responsiveness#16396
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
rhamilto:OCPBUGS-84967

Conversation

@rhamilto
Copy link
Copy Markdown
Member

@rhamilto rhamilto commented May 4, 2026

This is an manual cherry-pick of #16394

/assign rhamilto

Summary by CodeRabbit

  • New Features

    • Added integration test detection via user agent
    • Enhanced data view filtering with text-based search capabilities
    • Improved PodDisruptionBudget management and visualization
  • UI/UX Improvements

    • Renamed "Administrator" perspective to "Core platform" across the console
    • Updated OperatorHub references to "Software Catalog" for clearer operator discovery
    • Improved operator details pages with enhanced capability and infrastructure feature displays
    • Enhanced pagination UI with localized labels
    • Refined filter toolbar styling for better usability
  • Bug Fixes

    • Fixed snapshot status computation for consistent display
    • Improved namespace-aware pagination reset behavior
    • Enhanced Git service URL protocol and port handling for enterprise deployments
    • Refined telemetry handling for DevSandbox environments
    • Fixed form validation and project access workflows
  • Localization

    • Updated localization strings across all supported languages (English, Spanish, French, Japanese, Korean, Simplified Chinese)
    • Added new UI terms for improved clarity across multiple packages
  • Dependencies

    • Migrated from Yarn Classic to Yarn Berry with Corepack
    • Updated Node.js requirements to version 22+
    • Bumped PatternFly and other core dependencies to latest stable versions

…sponsiveness

The ConsoleDataView component was missing bottom pagination, which is
required by PatternFly design guidelines for proper mobile responsiveness.
On mobile viewports, the top pagination condenses to just an item count,
so full pagination controls must be available in the footer/bottom.

This change adds a Pagination component with variant="bottom" after the
DataViewTable to ensure pagination controls remain accessible on all
viewport sizes.

Additionally, adds complete i18n support to both top and bottom pagination
components with proper aria-labels for navigation buttons (first, previous,
next, last pages) and translated visible text (ofWord, itemsPerPage,
perPageSuffix) to ensure full accessibility and internationalization.

(cherry picked from commit 262fa86)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label May 4, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 4, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c07c14f0-53c8-4506-a051-31834088ffd8

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • expected dependent Jira Issue OCPBUGS-84963 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

This is an manual cherry-pick of #16394

/assign rhamilto

Summary by CodeRabbit

  • New Features

  • Added integration test detection via user agent

  • Enhanced data view filtering with text-based search capabilities

  • Improved PodDisruptionBudget management and visualization

  • UI/UX Improvements

  • Renamed "Administrator" perspective to "Core platform" across the console

  • Updated OperatorHub references to "Software Catalog" for clearer operator discovery

  • Improved operator details pages with enhanced capability and infrastructure feature displays

  • Enhanced pagination UI with localized labels

  • Refined filter toolbar styling for better usability

  • Bug Fixes

  • Fixed snapshot status computation for consistent display

  • Improved namespace-aware pagination reset behavior

  • Enhanced Git service URL protocol and port handling for enterprise deployments

  • Refined telemetry handling for DevSandbox environments

  • Fixed form validation and project access workflows

  • Localization

  • Updated localization strings across all supported languages (English, Spanish, French, Japanese, Korean, Simplified Chinese)

  • Added new UI terms for improved clarity across multiple packages

  • Dependencies

  • Migrated from Yarn Classic to Yarn Berry with Corepack

  • Updated Node.js requirements to version 22+

  • Bumped PatternFly and other core dependencies to latest stable versions

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 4, 2026
@openshift-ci openshift-ci Bot requested review from TheRealJon and cajieh May 4, 2026 23:16
@openshift-ci openshift-ci Bot added component/core Related to console core functionality kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 4, 2026
@rhamilto
Copy link
Copy Markdown
Member Author

rhamilto commented May 4, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • expected dependent Jira Issue OCPBUGS-84963 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

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.

Copy link
Copy Markdown
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 4, 2026
@rhamilto
Copy link
Copy Markdown
Member Author

rhamilto commented May 4, 2026

/verified by @rhamilto

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rhamilto: This PR has been marked as verified by @rhamilto.

Details

In response to this:

/verified by @rhamilto

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
Copy link
Copy Markdown
Member Author

rhamilto commented May 4, 2026

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 4, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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

@rhamilto
Copy link
Copy Markdown
Member Author

rhamilto commented May 5, 2026

/retest

@rhamilto
Copy link
Copy Markdown
Member Author

rhamilto commented May 5, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-84963 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-84963 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents
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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 5, 2026

@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-merge-bot openshift-merge-bot Bot merged commit 76c2db6 into openshift:release-4.21 May 5, 2026
8 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rhamilto: Jira Issue Verification Checks: Jira Issue OCPBUGS-84967
✔️ 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-84967 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:

This is an manual cherry-pick of #16394

/assign rhamilto

Summary by CodeRabbit

  • New Features

  • Added integration test detection via user agent

  • Enhanced data view filtering with text-based search capabilities

  • Improved PodDisruptionBudget management and visualization

  • UI/UX Improvements

  • Renamed "Administrator" perspective to "Core platform" across the console

  • Updated OperatorHub references to "Software Catalog" for clearer operator discovery

  • Improved operator details pages with enhanced capability and infrastructure feature displays

  • Enhanced pagination UI with localized labels

  • Refined filter toolbar styling for better usability

  • Bug Fixes

  • Fixed snapshot status computation for consistent display

  • Improved namespace-aware pagination reset behavior

  • Enhanced Git service URL protocol and port handling for enterprise deployments

  • Refined telemetry handling for DevSandbox environments

  • Fixed form validation and project access workflows

  • Localization

  • Updated localization strings across all supported languages (English, Spanish, French, Japanese, Korean, Simplified Chinese)

  • Added new UI terms for improved clarity across multiple packages

  • Dependencies

  • Migrated from Yarn Classic to Yarn Berry with Corepack

  • Updated Node.js requirements to version 22+

  • Bumped PatternFly and other core dependencies to latest stable versions

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 rhamilto deleted the OCPBUGS-84967 branch May 5, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. component/core Related to console core functionality jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants