New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CONSOLE-3922: Convert legacy ListPage to dynamic-plugin-sdk ListPage- components in Console VolumeSnapshots Storage #13560
Conversation
@cyril-ui-developer: This pull request references CONSOLE-3922 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this: 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. |
4fe0cc7
to
8182fac
Compare
3dee921
to
f891f7c
Compare
/retest |
291c797
to
95adeb4
Compare
95adeb4
to
0ed7fe2
Compare
/retest |
2 similar comments
/retest |
/retest |
@cyril-ui-developer: This pull request references CONSOLE-3922 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
@cyril-ui-developer: This pull request references CONSOLE-3922 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest |
3 similar comments
/retest |
/retest |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cyril-ui-developer, rhamilto, sg00dwin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR has been tested by using regression testing, no issue was found |
@cyril-ui-developer: This pull request references CONSOLE-3922 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
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. |
Adding labels as this is tech debt |
@rhamilto Thank you. |
/retest |
2 similar comments
/retest |
/retest |
/hold Revision f114037 was retested 3 times: holding |
/retest |
/unhold |
/retest |
@cyril-ui-developer: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
[ART PR BUILD NOTIFIER] This PR has been included in build openshift-enterprise-console-container-v4.16.0-202403141746.p0.g1ff7e80.assembly.stream.el8 for distgit openshift-enterprise-console. |
This change does not impact the UI screens but improve the code quality.
However the QA should verify the UI screens with the current ones.