kyma-project/busola

Cluster overview banner reappears after being dismissed — check local storage persistence

Open

#5,102 opened on Jun 25, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (66 forks)auto 404
area/busola/uxgood first issuekind/bug

Repository metrics

Stars
 (30 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The banners on the cluster overview page (e.g. "Meet Joule") can reappear after being dismissed. Dismissing a banner is supposed to store that action in local storage so it does not show again. The persistence logic may not be working correctly.

Expected result

Once a user dismisses a banner, it should not reappear on subsequent visits. The dismissed state should be correctly written to and read from local storage.

Actual result

According to a user report, the banner reappears after being dismissed. We have not been able to reproduce this independently, but the user confirmed it happens consistently.

Steps to reproduce

  1. Open Kyma Dashboard and navigate to the cluster overview page
  2. Dismiss one of the onboarding banners using the × button
  3. Reload the page or return to the cluster overview later

Troubleshooting

Reported by a user. Please verify that the logic is working correctly.

Contributor guide

Research direction
Investigate the banner dismissal logic on the cluster overview page. Check how dismissed banners are stored in local storage and where the persistence might fail. Look at the code that handles the dismiss action and the initial load of banners.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75