Skip to content

OBSINTA-1397: [release-coo-ocp-4.19] fix(perses): fall back to metadata.name when dashboard display name is missing#1009

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-coo-ocp-4.19from
openshift-cherrypick-robot:cherry-pick-1005-to-release-coo-ocp-4.19
Jun 23, 2026
Merged

OBSINTA-1397: [release-coo-ocp-4.19] fix(perses): fall back to metadata.name when dashboard display name is missing#1009
openshift-merge-bot[bot] merged 1 commit into
openshift:release-coo-ocp-4.19from
openshift-cherrypick-robot:cherry-pick-1005-to-release-coo-ocp-4.19

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1005

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.15

…s missing

Newly created PersesDashboard CRs show blank names in the list page
until the Perses operator reconciles them. Fall back to metadata.name
so dashboards are identifiable immediately. This matches the pattern
already used in useDashboardsData.ts and dashboard-import-dialog.tsx.

Signed-off-by: Raj Zalavadia <rzalavad@redhat.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot

openshift-ci-robot commented Jun 22, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OBSINTA-1397

Details

In response to this:

This is an automated cherry-pick of #1005

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.15

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 etmurasaki and jgbernalp June 22, 2026 16:07
@jgbernalp

Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp jgbernalp changed the title [release-coo-ocp-4.19] OBSINTA-1397: fix(perses): fall back to metadata.name when dashboard display name is missing OBSINTA-1397: [release-coo-ocp-4.19] fix(perses): fall back to metadata.name when dashboard display name is missing Jun 22, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 22, 2026
@openshift-ci

openshift-ci Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, openshift-cherrypick-robot

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 22, 2026
@openshift-ci

openshift-ci Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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.

@etmurasaki

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jun 23, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 23, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 23, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references OBSINTA-1397 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #1005

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.15

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 openshift-merge-bot Bot merged commit f1f7895 into openshift:release-coo-ocp-4.19 Jun 23, 2026
6 checks passed
@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@openshift-cherrypick-robot: new pull request created: #1011

Details

In response to this:

This is an automated cherry-pick of #1005

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.15

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.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants