mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-10 23:54:00 -05:00
Closed
opened 2026-04-10 18:33:34 -05:00 by GiteaMirror
·
3 comments
No Branch/Tag Specified
master
enforce-append-only-migrations-ci
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
claude/error-codes-worker-boundary-26i5uu
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
ai/simplify-categories-get-api
api-browser-custom-data-dir
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#8359
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 @CrazyKidJack on GitHub (Sep 14, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3438
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
There are many times where I don't want to have to assign a specific dollar amount to each category, but rather just to the group.
For example, I may have a group called "groceries" and within that categories for different types of grocery store items. Having the fine-grained categories is helpful to know exactly what i'm spending my money on which can help me make decisions in the moment... but when I'm actually doing my budget, I don't know exactly how many dollars I'm going to spend on produce vs junk food. I just know that total I want to spend say $200 on groceries. If I find I'm spending more than the $200, then I can look at the individual categories to figure out where that money is going and where I might be able to cut back.
Another way to explain: Imagine I put some of my envelopes (categories) into a bigger envelope. And some of the cash in the bigger envelope was not in any of the smaller envelopes? It's just sitting in the bigger envelope on its own, perhaps next to but not inside of the smaller envelopes. That is what I want to recreate.
If multi-level groups were ever implemented, I'd like the same idea to be applied to every level of grouping.
Describe your ideal solution to this problem
I think how it would work is self-explanatory except when multiple levels have budgeted amounts at the same time that do not add up to the same amounts.
I think the top-level group budget (and not the category budgets) should always be the thing that is used for the calculations in the cards at the top of the budget page.
If you don't assign a group budget, it automatically gets set to the sum of its child category budgets.
If you do assign a group budget, then there is the opportunity for a mismatch, which could be handled (I think intuitively) as follows:
In this case I think AB should force the group budget to be greater than or equal to the sum of the category budgets. This would allow users the option to
This would allow current users to keep using exactly how they have up until now with no change in behavior (if they never assign a budget to a group... then they will always default to equaling the sum of their categories... just like they do now)
But it would also allow users like me to decide, for each group, how specific we want to go with our budgeting independently of how specific we want to go with our spend tracking.
Side Note: I think it would also make sense to allow people to assign groups to a transaction instead of categories.
Teaching and learning
Would probably need to add some documentation to the budgeting docs about the 3 cases:
@github-actions[bot] commented on GitHub (Sep 14, 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 👍!
@CrazyKidJack commented on GitHub (Sep 14, 2024):
I did not select the checkbox for "Would you like to implement this feature?".
That said, I have significant development experience and would be willing to do so. But I would need/want significant assistance getting started navigating the AB code. Once I get going, I code quickly and (I like to think) with high quality... but I always have a hard time getting into other people's code, figuring out how it works, and figuring out the best way to set up the dev environment for that project. It's really a momentum problem. If someone could help guide me to a point where I understand the code base, then I would be more than happy to hop in on this and also other features.
@wetrustinprize commented on GitHub (Jul 16, 2025):
Would really like to see this in Actual, currently I just have 3 categories to follow the 50/30/20 rule, but I can't have a fine report about my expenses since they are just three categories.