mirror of
https://github.com/actualbudget/actual.git
synced 2026-11-13 17:43:23 -06:00
[Feedback]: Budget Analysis report #2850
Open
opened 2026-02-28 20:30:39 -06:00 by GiteaMirror
·
14 comments
No Branch/Tag Specified
master
matiss/enable-banking-pending-and-rate-limit
claude/lucid-turing-br8zwl
jfdoming/api-key-shared-bank-sync
worktree-pr-description-rules
ios-ci-launch-test
worktree-count-points-gh-bot
theme-number-contrast
theme-contrast-test
fix/automatic-bank-sync-mobile-app
future-buffer
carryover-chain
copilot/fix-failing-github-actions-job
copilot/fix-failing-github-actions-job-compare
fix/hide-sab-warning-in-capacitor
release
tabedzki/feat/docker-non-root
ios-home-screen-widgets
mobile-budget-redesign
ai/fix-mobile-carryover-arrow-alignment
jfdoming/provider-identity-update
jfdoming/electron-signin-update
jfdoming/openid-flow-update
release-update/26.10.1
release-notes/26.10.1
matiss/dazzling-babbage-b9rjwi
react-query-rules
ai/add-loan-formula-autocomplete
claude/pr-8519-regression-testing-fhvrrh
speed-up-transaction-list-and-schedules
fix-slow-balance-recompute-on-transaction-edit
jfdoming/opfs-sahpool-mobile
jfdoming/opfs-sahpool
fix-8612-schedule-delete-menu
jfdoming/api-tokens-part-8
jfdoming/api-tokens-part-7
jfdoming/api-tokens-part-6
jfdoming/api-tokens-part-5
jfdoming/mobile-safe-area-header
jfdoming/api-tokens-part-4
jfdoming/mobile-splash-lifecycle
jfdoming/api-tokens-part-3
jfdoming/mobile-shared-array-buffer
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-1
persist-transaction-filters
claude/modernize-transactions-tanstack-orgrze
bank-sync-per-file-03-pluggy-loot-core
claude/auto-close-prs-no-profile-pic-mjqpsy
cross-version-sync-stage2
claude/react-table-library-research-afx83z
tolerate-newer-migrations
claude/verify-migration-guardrails-i82c8m
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
cross-version-sync-compat
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
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
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.11.0
v26.10.0
v26.9.0
v26.8.1
v26.8.0
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 labels
feedback
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2850
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.
Originally created by @youngcw on GitHub (Jan 21, 2026).
Add all feedback for the Budget Analysis report here. Original PR #6137
@Juulz commented on GitHub (Jan 25, 2026):
Thank you for your work on this!
Balance is using numberNeutral. That is mostly set for zeros and is set to be the same as pageTextSubdued and is really hard to see. There are already variables to use, reportsBlue or reportsGray that would show up well.
Actual Light Theme
@youngcw commented on GitHub (Jan 26, 2026):
@Juulz Feel free to put in a PR for that since the colors are new all over
@sexyskinnybitch commented on GitHub (Feb 2, 2026):
Can this also take into account when "cover overspending" was used? I never leave any categories over spent at month end, I always cover any overspending from some other category, but it still should report that it was overspent. The details are logged in the month notes, so it shouldn't be all that hard to figure it out.
example:
I budget $100 for eating out, spend $120. I use the cover overspending to pull $20 from my grocery category to cover the overspending. I want to be able to see that I did in fact over spend in the eating out category, even though I covered it before month end.
@niffelheimba commented on GitHub (Feb 3, 2026):
I love the overall idea of this widget, but I think there should be an option to have the bars overlap/stacked. I think default layout makes for a poor experience trying to view all four bars for every month, for two main reasons:
@Juulz commented on GitHub (Feb 4, 2026):
I also think the report would be easier to read if all of the values were absolutes.
@youngcw commented on GitHub (Feb 4, 2026):
The problem with absolute bars is what if the spending total is positve? Like you received a large refund or something. The current bars match the cashflow report
@skynet-gh commented on GitHub (Feb 5, 2026):
The widget only shows 6 months on Reports, even when you click through, change to 1 year, and save.
@tabedzki commented on GitHub (Feb 5, 2026):
I don't believe there's a way to take into account the amount that you additionally allocated to cover the overspending. In the example provided, the $120 becomes the new budgeted amount. @youngcw can you correct me if I'm wrong?
I understand where you're coming from. Would you be able to provide your feedback on #6877, which is deployed here.
The one problem we'll have to tackle is transparency/overlap since I was able to concoct a Budget.zip wherein the Spent bar is hidden behind Overspending Adj bar (December 2025 in the test budget).
This should be fixed in #6875. Can you take a look at it here?
@sexyskinnybitch commented on GitHub (Feb 5, 2026):
It could be done if the month notes are parsed. All the "cover overspending" is logged there.
Dana
They/Them
2026-02-05T21:38:20Z tabedzki @.***>:
@skynet-gh commented on GitHub (Feb 5, 2026):
@tabedzki yep #6875 fixes it!
@Juulz commented on GitHub (Feb 5, 2026):
While true, I think that scenario is an outlier. Perhaps a choice in the report?
@youngcw commented on GitHub (Feb 5, 2026):
I think per category it wont be especially uncommon. On a whole budget scale, yes, per category, no.
@tabedzki commented on GitHub (Feb 6, 2026):
Easiest example I can think of is cancelling a trip or flight in a later month; any refund is likely to cause the category to be positive, especially if you're not buying flights frequently.
I don't know much about the month notes and parsing them. If you have knowledge with them, I'd appreciate the support on getting this implemented.
@sexyskinnybitch commented on GitHub (Feb 6, 2026):
Sadly, my coding skills don't apply to this.
Dana
They/Them
2026-02-06T00:11:51Z tabedzki @.***>: