mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
Closed
opened 2026-05-29 13:58:26 -05:00 by GiteaMirror
·
9 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
No Label
bug
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#99170
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 @Bsmith85282 on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4116
Verified issue does not already exist?
What happened?
The Issue: In the tracking budget with roll over - columns don't seem to add up correctly. Even after reading the documentation found at https://actualbudget.org/docs/getting-started/tracking-budget/ - under "How Money Rolls Over" It doesn't make sense that money in a rollover row from the "Budgeted" column would move to the 'Spent" column (shown in RED), and money in the spent column doesn't go towards spent totals (GREEN). Budgeted non roll over seems to work normally (YELLOW).
This also affects the "Balance" Column (no color).
I would expect each Column to total everything in that column. If looking at picture attached I would expect Budgeted to total up to 450.00 and Spent to total up to -23.81 and the balance column should add the two:
450 [Budgeted] + (-23.81) [Spent] = 426.19 [Balance]
Note I Cannot select more than one OS in the drop down but had this on both Mac OSX and Windows 11 Safari/Brave Respectively. This issue does not appear to be present on GitHub however, I did post in discord.
How can we reproduce the issue?
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Windows 11
@youngcw commented on GitHub (Jan 9, 2025):
Are there any categories that you stopped carrying forward in that shown month?
It will be a lot easier to confirm and try to fix anything if you can upload an example file. It can be a demo file.
@Bsmith85282 commented on GitHub (Jan 9, 2025):
There was nothing that I stopped carrying over - everything with the -> by it was set to rollover.
I will try to upload a file later today for you!
@youngcw commented on GitHub (Jan 15, 2025):
Are you going to upload an example budget? If not Ill close this ticket.
@youngcw commented on GitHub (Jan 16, 2025):
One thing you can maybe try is to change to envelope budget then change back to a tracking budget. For some reason that fixed someone else's spent total issues.
@arekmano commented on GitHub (Feb 5, 2025):
Chiming in as this is indeed occurring out in the wild. I've set up a minimal PoC here, to demonstrate the issue
100$ budget, 100$ spent , no rollover. Expenses and savings are as expected

100$ budget, 100$ spent, rolled over to the following month. Expense disappears. Its as if I never spent that money

@youngcw. What am I doing wrong here? Alternatively, what additional information would you need to track down the potential bug?
I've included the sample PoC budget in this comment
2025-02-04-My Finances 1.zip
@Thafar commented on GitHub (Feb 13, 2025):
I see the same behavior as @Bsmith85282, the spent for a rollover category in a tracking budget seems broken:

It seems that the rollover behavior in a tracking budget is primarily based on changes in balance:
Not sure what is the reasoning behind this, but in my opinion it gives very unexpected behavior:
In the example below, I paid $100 twice and received $100 twice. So I spent/saved nothing.
Besides that, I budgeted $50 in October.
Now the overview tells me I saved $250 since my balance got increased by $150 in October and $100 in December.
In my opinion, rollover categories should either:
Interested to hear how others see this.
@Mpic commented on GitHub (Feb 23, 2025):
This seems related to https://github.com/actualbudget/actual/issues/4321, and I can't make sense of the current behavior either :-/
I really would like to be able to use the tracking mode, but this needs clarification or fixing :-/
@youngcw commented on GitHub (Mar 12, 2025):
Hi everyone. We are trying to improve the tracking budget math. You can try it out at #4567.
It makes the table totals not be dependent on the carryover state, and excludes hidden categories/groups from totals.
@arekmano commented on GitHub (Apr 6, 2025):
I spent some time running through the example above (and various permutations of it), using the PRs latest commit (
c1b5eabb6f). All the interactions are as I would expect them; rollover doesn't impact totals in the same odd way as it would previously, and values are as I'd expect them.Thanks for spending the time to fix the issue! Looks good so far 👍