makeplane / makeplane/plane

[feature]: Notification Inbox should be a pop over

Open
#9,314 1 comment 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Jun 25, 2026.

✨feature plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Right now, clicking the notifications icon takes you to a full page inbox view. That pulls you completely out of whatever you were doing just to glance at what came in. The proposal is to make notifications open as a popover anchored to the bell, showing a quick summary of recent items. Clicking an individual item then opens that specific ticket, PR, or comment in the normal UI, scrolled or linked directly to the relevant comment the notification was about.
In short: a lightweight popover for triage, and a direct jump to context when you actually want to act on something.

Why should this be worked on?

The current flow has a real cost to focus. Checking notifications is usually a quick "is anything on fire" glance, but the full page inbox treats every check like a deliberate context switch. You lose your place, your scroll position, and your mental state on whatever you were reviewing or writing. For a tool people keep open all day, that friction adds up across dozens of checks.

A popover fixes the common case without changing the powerful one. Most notification checks are triage: skim, decide nothing needs attention, get back to work. A popover lets you do that in place and dismiss it with a click or an escape key, never leaving your current page. The full inbox can still live behind a "see all" link for when you genuinely want to sit down and process everything.

It also matches what people already expect. Slack, Linear, GitLab, and most modern tools use exactly this pattern for notifications. The full page redirect feels dated by comparison, and new users coming from those tools hit the friction immediately.

Finally, the deep link on click closes the loop properly. A notification is about a specific comment or event, so landing on that exact spot in the normal UI is more useful than landing in an inbox that just re-summarizes it. Fewer clicks between "something happened" and "I am looking at the thing that happened."

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.