mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-17 08:32:41 -05:00
Closed
opened 2026-04-10 18:19:05 -05:00 by GiteaMirror
·
6 comments
No Branch/Tag Specified
master
cross-version-sync-stage2
claude/transaction-column-manager-cp0u0w
claude/verify-migration-guardrails-i82c8m
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#8125
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @PartyingChair on GitHub (Jul 2, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2963
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I find it difficult to see if or where I’ve overspent in a category
Describe your ideal solution to this problem
As someone coming from YNAB due to price increase I do really love how YNAB has a huge banner at the top saying “OVERSPENT CATEGORY” when I’ve overspent in a category. I don’t need this to copy YNAB exactly, but a clear indication of an overspending would be nice.
Also, I can open a second feature request for this if necessary, but I think notifications, either from the web app or SMTP email or pushover would all be a nice quality of life improvement. Overspending or new transaction from a schedule would be ideal in my opinion.
Thank you
Teaching and learning
I think this is mostly a UI change and doesn’t need much documentation. Just a banner or some UI element to let me know 1) I have overspending and 2) where that overspending is
@github-actions[bot] commented on GitHub (Jul 2, 2024):
✨ Thanks for sharing your idea! ✨
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
@joel-jeremy commented on GitHub (Apr 15, 2025):
Partially implemented in https://github.com/actualbudget/actual/pull/4643
@joel-jeremy commented on GitHub (Apr 15, 2025):
Closing https://github.com/actualbudget/actual/issues/3667 as duplicate which has 7 votes
@joel-jeremy commented on GitHub (May 6, 2025):
This would be easier to implement now in desktop with the introduction of
useOverspentCategorieshook. The hard part is to figure out where to put the banner to provide the best UX. We need to take in consideration multi-month budget view.@youngcw commented on GitHub (May 6, 2025):
I like the idea of having a "group" on the budget table that is for uncategorized transactions. So same size as a category group line, but probably a different color. Or just a banner like thing as the first entry in the table that is for uncategorized things.
My only concern with adding this, is that it might give people a mechanism for not categorizing things
@Juulz commented on GitHub (May 18, 2025):
Perhaps... banner or flag (better IMO) the month name and put a line in the dropdown (perhaps in red) with the amount and a link to a filtered view.