github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #6539] [Bug]: excessive notifications #17005

New Issue
Closed
opened 2026-04-14 19:58:31 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-14 19:58:31 -05:00
Owner
Copy Link

Originally created by @danielkerwin on GitHub (Jan 3, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6539

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If you’re on mobile and are doing the budget, often you can quickly move down items and tap the average of x to set the budget.

Every action triggers a notification (they are not informative notifications in my opinion) and the delay is too slow.

This leads to multiple notifications appearing if you work fast and results in either more clicks to dismiss useless notifications or having to wait.

Overall it’s a poor experience and we should let users disable notifications, change delay, or just remove them from this action. Ideally the notifications shouldn’t stack vertically, they should stack on the z-axis so they don’t ruin the screen experience

Image

How can we reproduce the issue?

Trigger multiple budget actions quickly on mobile.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

Mobile Device

Originally created by @danielkerwin on GitHub (Jan 3, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6539 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? If you’re on mobile and are doing the budget, often you can quickly move down items and tap the average of x to set the budget. Every action triggers a notification (they are not informative notifications in my opinion) and the delay is too slow. This leads to multiple notifications appearing if you work fast and results in either more clicks to dismiss useless notifications or having to wait. Overall it’s a poor experience and we should let users disable notifications, change delay, or just remove them from this action. Ideally the notifications shouldn’t stack vertically, they should stack on the z-axis so they don’t ruin the screen experience <img width="590" height="1278" alt="Image" src="https://github.com/user-attachments/assets/4576a7c1-c2b5-4a57-979f-7add6d7b70b5" /> ### How can we reproduce the issue? Trigger multiple budget actions quickly on mobile. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System Mobile Device
GiteaMirror added the responsivegood first issuebug labels 2026-04-14 19:58:32 -05:00
GiteaMirror commented 2026-04-14 19:58:33 -05:00
Author
Owner
Copy Link

@db-src commented on GitHub (Jan 4, 2026):

Indeed, control over whether and how long to show notifications would be very desirable. I will undo things manually if I want to, personally, so they do nothing for me really!

Additionally it's a bit confusing that the X on these notifications is on the opposite side to that on the banner for how many txns are currently selected, given that the latter can trigger the former (select then Clear, for example).

<!-- gh-comment-id:3708318512 --> @db-src commented on GitHub (Jan 4, 2026): Indeed, control over whether and how long to show notifications would be very desirable. I will undo things manually if I want to, personally, so they do nothing for me really! Additionally it's a bit confusing that the X on these notifications is on the opposite side to that on the banner for how many txns are currently selected, given that the latter can trigger the former (select then Clear, for example).
GiteaMirror commented 2026-04-14 19:58:34 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 4, 2026):

TBh I aggree. It would be great if the notifications "stacked". So you only ever see one. And if you undo the top one, it shows the previous one.

And the design of them could also be improved so they take less screen space.

PR to do improvements here are welcome!

<!-- gh-comment-id:3708323138 --> @MatissJanis commented on GitHub (Jan 4, 2026): TBh I aggree. It would be great if the notifications "stacked". So you only ever see one. And if you undo the top one, it shows the previous one. And the design of them could also be improved so they take less screen space. PR to do improvements here are welcome!
GiteaMirror commented 2026-04-14 19:58:35 -05:00
Author
Owner
Copy Link

@danielkerwin commented on GitHub (Jan 5, 2026):

TBh I aggree. It would be great if the notifications "stacked". So you only ever see one. And if you undo the top one, it shows the previous one.

Yes, this is what I'd like to see, pretty common for modern web apps.

I've pulled the code and started a branch to implement this - here's the before and after for feedback before I open a PR.

Example (with style changes to make the UX more compact and more consistent with other component styles)
Image

Image

Demo videos:
BEFORE - horizontally stacked notifications
https://github.com/user-attachments/assets/df346d78-dcea-49a9-911f-3e72fa23159e

AFTER - z-axis stacked notifications with vertical, opacity and scale offsets (max 3 visible at any time) (excludes UX styling tweaks)
https://github.com/user-attachments/assets/349a93e9-c6a6-43d8-a8cc-60f265d8394c

<!-- gh-comment-id:3708613417 --> @danielkerwin commented on GitHub (Jan 5, 2026): > TBh I aggree. It would be great if the notifications "stacked". So you only ever see one. And if you undo the top one, it shows the previous one. Yes, this is what I'd like to see, pretty common for modern web apps. I've pulled the code and started a branch to implement this - here's the **before** and **after** for feedback before I open a PR. Example (with style changes to make the UX more compact and more consistent with other component styles) <img width="331" height="470" alt="Image" src="https://github.com/user-attachments/assets/faf09d27-5db8-42c0-ba95-1a26d704c489" /> <img width="335" height="563" alt="Image" src="https://github.com/user-attachments/assets/a5f63bae-bec0-4122-8d9b-9371c1205caf" /> Demo videos: **BEFORE** - horizontally stacked notifications https://github.com/user-attachments/assets/df346d78-dcea-49a9-911f-3e72fa23159e **AFTER** - z-axis stacked notifications with vertical, opacity and scale offsets (max 3 visible at any time) (excludes UX styling tweaks) https://github.com/user-attachments/assets/349a93e9-c6a6-43d8-a8cc-60f265d8394c
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug good first issue responsive
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#17005
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?