mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
Closed
opened 2026-04-18 03:03:37 -05:00 by GiteaMirror
·
10 comments
No Branch/Tag Specified
master
claude/verify-migration-guardrails-i82c8m
cross-version-sync-stage2
api-browser-custom-data-dir
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#26732
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 @gravelfreeman on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2376
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I spent quite some time adding all my upcoming payments under the Schedules tab. After adding my schedules to a category by modifying the rule, I was surprised that I had to manually add them in the Budgeted column.
I think the current behaviour is so that the schedule task creates an entry in the database and then that expense will appear under the Spent column prior to the category line you've set the rule to.
The same logic should apply to the Budgeted column; since I know it'll be an expense and that I took the time to add it as a schedule, I'm expecting to see it there, without manual intervention.
Describe your ideal solution to this problem
Update automatically the Budgeted column based on the upcoming Schedules.
Teaching and learning
In reference of this.
@github-actions[bot] commented on GitHub (Feb 19, 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 👍!
@Teprifer commented on GitHub (Feb 19, 2024):
This makes sense, I think it'd be best tied into the goal templates feature whenever progress indicators are added. Then the scheduled transaction can be budgeted via that, and alerting a category is under budgeted for the expected schedules could be displayed.
This would hook into the one click budgeting templates allows for.
I think an outright auto budgeting shouldn't be done as there are many not in a position to budget a whole month at a time, and budgeting early before their next pay comes in would create a negative budget.
@Teprifer commented on GitHub (Feb 19, 2024):
To add a missing thought, could auto add the goal templates for schedules automatically if a category is assigned as a rule.
@gravelfreeman commented on GitHub (Feb 19, 2024):
At least if we can have a toggle switch as an option to add to budgeted column for the one that wants it.
@javripley commented on GitHub (Feb 19, 2024):
Personally, I'd rather have the budget UI displaying upcoming expenses (so that I can budget ahead for those) rather than automatically setting that amount aside, "just" because I scheduled the transaction. That way you wouldn't be mislead into thinking you will have/not have that money available at the end of the month, since it would be clearly shown that some expenses/incomes are upcoming. I think automated rules for budgeting, unless explicitly set for that, can get confusing real quick.
@gravelfreeman commented on GitHub (Feb 19, 2024):
Another column actually make a lot of sense. I would think it's even better this way! Good idea.
@gravelfreeman commented on GitHub (May 2, 2024):
I would like to know why my suggestion is marked as Closed? I was doing my budget and saw that it was still not possible to do this 😞 I would really like to see this feature coming!
@youngcw commented on GitHub (May 2, 2024):
Its closed because of this comment
@TorC8 commented on GitHub (Aug 11, 2025):
This would be a significant improvement, and best in the form of updating the budget page to a four-column layout. Budgeted, Spent, Upcoming, and Balance, with the balance reflecting both spent and upcoming.
I think the most useful number for budget balance is how much is available to spend, particularly in the case of a category that has a mix of subscriptions and one-off purchases. As it is now, I don't see an easy way to get AB to tell me how much I can spend in a category without going over budget by the end of the month.
Budget view as of the thirteenth with $15 spent on the third and a $90 transaction scheduled for the twenty fifth:
Example current:
Budgeted: $200
Spent: $15
Balance: $185
Proposed change example:
Budgeted: $200
Spent: $15
Scheduled: $90
Balance: $95
I suppose one could separate further:
Budgeted: $200
Spent: $15
Current bal: $185
Scheduled: $90
EoM balance: $95
IMHO, the last example is excessive and the current balance should be an optional view if implemented at all.
@TorC8 commented on GitHub (Aug 11, 2025):
I started looking at this, but I'm not entirely sure where to find the relevant files. Looks like it should be fairly easy, unless the relevant information isn't available to grab from.
First, function to get the needed upcoming transaction data:
for rule
if $rule action includes set category to $category AND if $schedule is upcoming when upcoming length is end of this month
let upcomingspend += $amount
Second, change the budget view page to include the fourth column, print the output of of the above function in it, and change budget balance column display to reflect this additional value.
Would someone familiar with the code let me know if I'm on the right track and if so, point me toward the files to look at?