Skip to content

[release-4.21] OCPBUGS-78599: Migrate InstallPlan components table to PatternFly Table#16159

Open
rhamilto wants to merge 1 commit intoopenshift:release-4.21from
rhamilto:OCPBUGS-78600
Open

[release-4.21] OCPBUGS-78599: Migrate InstallPlan components table to PatternFly Table#16159
rhamilto wants to merge 1 commit intoopenshift:release-4.21from
rhamilto:OCPBUGS-78600

Conversation

@rhamilto
Copy link
Member

Summary

Migrates the InstallPlan components table from raw HTML table elements to PatternFly v6 Table components, improving consistency and accessibility across the OLM package UI.

Changes

  • Replaced HTML <table>, <thead>, <tbody>, <tr>, <th>, <td> elements with PatternFly v6 components: <PFTable>, <Thead>, <Tbody>, <Tr>, <Th>, <Td>
  • Updated install-plan.tsx to use the PatternFly Table API
  • Maintains existing functionality while adopting PatternFly design system standards

Test plan

  • View InstallPlan details page with resolved components
  • Verify the components table displays correctly
  • Test table sorting and interaction
  • Verify modal preview for component resources still works
  • Check responsive behavior on different screen sizes

🤖 Generated with Claude Code

Replace HTML table markup with PatternFly Table components in the
InstallPlanPreview component. Also replace the raw co-m-pane__body div
wrapper with the proper PaneBody component for consistency.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 17, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
  • expected Jira Issue OCPBUGS-78253 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

Migrates the InstallPlan components table from raw HTML table elements to PatternFly v6 Table components, improving consistency and accessibility across the OLM package UI.

Changes

  • Replaced HTML <table>, <thead>, <tbody>, <tr>, <th>, <td> elements with PatternFly v6 components: <PFTable>, <Thead>, <Tbody>, <Tr>, <Th>, <Td>
  • Updated install-plan.tsx to use the PatternFly Table API
  • Maintains existing functionality while adopting PatternFly design system standards

Test plan

  • View InstallPlan details page with resolved components
  • Verify the components table displays correctly
  • Test table sorting and interaction
  • Verify modal preview for component resources still works
  • Check responsive behavior on different screen sizes

🤖 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.

@openshift-ci openshift-ci bot requested review from jhadvig and spadgett March 17, 2026 12:36
@openshift-ci openshift-ci bot added component/olm Related to OLM approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 17, 2026
@rhamilto rhamilto changed the title OCPBUGS-78253: Migrate InstallPlan components table to PatternFly Table [release-4.21] OCPBUGS-78253: Migrate InstallPlan components table to PatternFly Table Mar 17, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 17, 2026

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: 77a39478-8c19-4536-98b4-49bc8b0e5db0

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
📝 Coding Plan
  • Generate coding plan for human review comments

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

@rhamilto rhamilto changed the title [release-4.21] OCPBUGS-78253: Migrate InstallPlan components table to PatternFly Table [release-4.21] OCPBUGS-78600: Migrate InstallPlan components table to PatternFly Table Mar 17, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-78253 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:

Summary

Migrates the InstallPlan components table from raw HTML table elements to PatternFly v6 Table components, improving consistency and accessibility across the OLM package UI.

Changes

  • Replaced HTML <table>, <thead>, <tbody>, <tr>, <th>, <td> elements with PatternFly v6 components: <PFTable>, <Thead>, <Tbody>, <Tr>, <Th>, <Td>
  • Updated install-plan.tsx to use the PatternFly Table API
  • Maintains existing functionality while adopting PatternFly design system standards

Test plan

  • View InstallPlan details page with resolved components
  • Verify the components table displays correctly
  • Test table sorting and interaction
  • Verify modal preview for component resources still works
  • Check responsive behavior on different screen sizes

🤖 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.

@rhamilto
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-78253 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.

@rhamilto rhamilto changed the title [release-4.21] OCPBUGS-78600: Migrate InstallPlan components table to PatternFly Table [release-4.21] OCPBUGS-78599: Migrate InstallPlan components table to PatternFly Table Mar 17, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-78390 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
  • expected dependent Jira Issue OCPBUGS-78390 to target a version in 4.22.0, but it targets "4.21.z" 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

Migrates the InstallPlan components table from raw HTML table elements to PatternFly v6 Table components, improving consistency and accessibility across the OLM package UI.

Changes

  • Replaced HTML <table>, <thead>, <tbody>, <tr>, <th>, <td> elements with PatternFly v6 components: <PFTable>, <Thead>, <Tbody>, <Tr>, <Th>, <Td>
  • Updated install-plan.tsx to use the PatternFly Table API
  • Maintains existing functionality while adopting PatternFly design system standards

Test plan

  • View InstallPlan details page with resolved components
  • Verify the components table displays correctly
  • Test table sorting and interaction
  • Verify modal preview for component resources still works
  • Check responsive behavior on different screen sizes

🤖 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.

@rhamilto
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-78390 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
  • expected dependent Jira Issue OCPBUGS-78390 to target a version in 4.22.0, but it targets "4.21.z" 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.

@rhamilto
Copy link
Member Author

/jira refresh
/test backend

@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-78390 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
/test backend

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
Contributor

openshift-ci bot commented Mar 17, 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.

@rhamilto
Copy link
Member Author

/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 Mar 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

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/olm Related to OLM jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants