Summary

In Jira Cloud, the notification bell in the top navigation does not always reflect the latest unseen notification count when working across multiple tabs or when returning to Jira after viewing another tab/application. Users must often reload the page to see an accurate count.

This request is to improve the notification bell so that the unseen count is refreshed when a Jira tab becomes active again, without requiring a manual page reload.

---

Problem / Pain Points

Today, users commonly:

• Work with multiple Jira tabs open (for issues, boards, backlogs, dashboards, etc.).

• Open the notification bell in one tab and read/clear notifications there.

• Move between different Jira tabs or to other browser tabs during their work.

Observed behaviour:

• After reading notifications in one tab, other Jira tabs continue to show an outdated unseen count in the bell.

• Returning to an existing Jira tab (after some time on another tab/app) often shows a stale notification count.

• The bell only shows the correct number after the user manually reloads the page, or waits for an internal background refresh that may be delayed or skipped depending on tab activity.

Impact on users:

• The notification bell becomes unreliable as a quick indicator of whether there is new, unseen activity.

• Users with many Jira tabs feel they must reload multiple pages just to “clear” the notification count.

• This is especially confusing because some other parts of Jira UI can update more quickly or “live”, setting an expectation that the bell should also keep up.

---

Desired Behaviour

The goal is to keep the notification bell unseen count in sync with the user’s true unread state, without requiring manual page reloads, while still respecting performance and cost constraints.

Specifically:

1. When returning to a Jira tab, the notification bell should refresh to reflect the latest unseen count shortly after the tab becomes active/visible again.

1. This should apply to scenarios such as:

• • Switching between different Jira tabs in the same browser window.

• • Moving from another website or application back to a Jira tab that was already open.

1. The behaviour should reduce or eliminate situations where:

• • A user has already read notifications in one tab,

• • Yet other Jira tabs continue to show the previous count (or no badge) for an extended period of time until a full reload.

This request is not specifically asking for full real‑time, push‑based updates across tabs (such as websockets or subscriptions). The primary ask is to refresh the notification bell on tab focus/visibility change, so the count is reasonably up to date whenever the user returns to Jira.