mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 20:23:07 -05:00
[Feedback] Release Report Budget #1205
Closed
opened 2026-02-28 19:35:56 -06:00 by GiteaMirror
·
23 comments
No Branch/Tag Specified
master
matiss/oxlint-no-floating-promises-require-array-sort-compare
ai/custom-theme-dual-prefs
claude/fix-simplefin-batch-sync-O8LcD
matiss/fix-6804
claude/fix-simplefin-ssrf-T31gX
claude/release-notes-validation-X7rvR
add-claude-github-actions-1772738270730
react-query-rules
react-query-useSchedules
matiss/separate-lint-format
dependabot/npm_and_yarn/ajv-6.14.0
cursor/sync-performance-notification-9899
react-query-prefs
matiss/chunked-sync-and-progress-ux
v26.2.1
copilot/sub-pr-6880
fix-react-query-clear-on-close-budget
copilot/sub-pr-6140
feat/auto-note
feat/scoped-bank-sync
cursor/desktop-transactions-react-table-1d0c
fix-exhaustive-deps-App
copilot/fix-find-replace-bug
release/v26.2.0-pre
matiss/browser-tests
mobile-fix-drag-and-drop-across-groups
budget-table-v2
PayeeAutocomplete2
pglite
bugfix/plugins/fix-plugins-sw
feat/plugins/plugins-core-package
prerelease
matiss/unicode-minus-fix
cursor/fix-actual-github-issue-6206-gemini-3-pro-preview-9c37
TransactionFormPage
cursor/implement-mortgage-and-loan-account-type-78ca
tests-update-fill-with-pressSequentially
mobile/link-modal
deps/25.11
cursor/fix-update-vrt-apply-ci-job-dispatch-b324
sync-server-plugins
cursor/propose-patch-for-github-issue-5680-2a18
fix/compiler-preserve-inner-dollar-escapes
cursor/analyze-actual-budget-issue-and-propose-fix-5b70
coderabbitai/docstrings/0c070e5
cursor/add-wip-prefix-and-comment-to-prs-d78d
jfdoming/08-21-auto-focus-on-navigate-in-all-browsers
show-totals-on-mobile-budget-banners
allow-child-transactions-make-transfer
mobile-calculator-keyboard
payee-geolocation
enhance/restore_scroll_position
dm-fix-second-click-on-mobile-new-transaction-2
scrollToLocationBudget
alert-autofix-38
tsconfig-composite
mobile-fix-uncategorized-transactions-on-tracking-budgets
server-budget-handlers
fix-sql-injection-in-cleanup-template
non-chrome-draggable-workaround
mobile-budget-page-swipe-navigation
ts-db-all
stable
dark-theme-with-brand-colors
fix-mobile-delete-group
ts-db-select
UnderKoen/reconcile-context-menu
master-before-server-merge
v25.2.1
ts-runQuery
rename-redux-hooks
UnderKoen/3557-persist-state-in-history
remove-redux-CLOSE_BUDGET
fix-exhaustive-deps-errors-FinancesApp
redux-toolkit-createSlice-backup
accounts-function-component
ts-useSplitsExpanded
loot-core-server-package
useTransactios-in-TransactionEdit
react-aria-input
move-redux-to-desktop-client
QueryState-type
fix-themes-applied-late
mobile-vrts
revert-3295-spendingCardFix
react-aria-button-4
split-payee-on-mobile
twk3/pin-apis-crdt
notes-tag-autocomplete
ts-LoadBackup
dnd-kit
package-upgrades
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
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#1205
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 @youngcw on GitHub (Jul 7, 2024).
The Report Budget option needs just a few things before it can be released fully.
@Teprifer commented on GitHub (Jul 7, 2024):
To the last optional point on naming, not too fussed, but Traditional doesn't quite seen right, since while kinda true, it's also less descriptive and is suggestive it should be preferred. Could be 'Tracking' and 'Envelope'?
I also think the envelope should have (Default) or (Recommended) beside it when selecting type in keeping with Actual's history and being the primary budget type. It's also what actual is most known for (a YNAB alternate).
@jsehnoutka commented on GitHub (Jul 7, 2024):
Not sure if Budget types are meant to be interlinked, I've always used them as complementary to each other. But if yes, I would suggest looking into #732. Maybe a dropdown menu of the Report budget could be extended with "Synchronize budgets" button?
@MatissJanis commented on GitHub (Jul 9, 2024):
TBH I think we shouldn't do this. We should be removing steps from the onboarding flow, not adding more.
@psybers commented on GitHub (Jul 11, 2024):
I'm not sure dropping the rollover capability is a good idea. I am not sure how other people are using this, but that is still needed for me for a few categories (that typically have yearly or bi-yearly charges). Otherwise you really can't budget for those without some sort of rollover.
@psybers commented on GitHub (Jul 11, 2024):
FYI I started work on having hidden categories not affect this budget. I have two bugs I am tracking down and then I will probably PR that.
@youngcw commented on GitHub (Jul 17, 2024):
I don't think a selector is needed, but I think people would like the option to set a name upon budget creation. If we do that, then its not a big deal to also add a type selector imo.
@MatissJanis commented on GitHub (Jul 17, 2024):
Is budget name critical to get started? I would argue - no, it's optional. The onboarding should have as little friction as possible in order to allow new users to try out the product without needing to fill out forms and/or make decisions that could be made at a later date. Just click "try now" -> import an existing budget -> boom, you're ready to try it out. Simple as that.
@youngcw commented on GitHub (Jul 26, 2024):
The only reason I would like to drop the ability is that the math for the budget totals gets weird. So if that could be made less weird, or the docs updated to make understanding those numbers easier, that would be fine with me.
@MatissJanis commented on GitHub (Sep 2, 2024):
Feedback: https://github.com/actualbudget/actual/issues/3346
@57194 commented on GitHub (Sep 30, 2024):
I was wondering the state of the "tracking budgeting" feature. Is it safe to start using it today, or should I expect significant changes to it (changes that could wipe all my data) and not bother using it yet?
I know it's in the "experimental" settings section, but I don't see any huge complaints from folks other than naming and some slight confusion on some of the displayed information.
Thanks.
Edit: I don't use Discord (and don't plan on it), so apologies for bringing discussion-type questions here, rather than feedback.
@psybers commented on GitHub (Sep 30, 2024):
@57194 I have been using it for a year and it is quite stable. You shouldn't lose data.
I would say it is pretty close to moving out of experimental. I personally would like to see hidden categories not affect the tracking budget, but other than that I see no problems with it in its current form.
@57194 commented on GitHub (Sep 30, 2024):
Thanks for the quick answer, @psybers! That seems to answer what I was wondering. If it was still very early stages with sweeping changes planned, then I wasn't gonna bother using Actual yet; but if the core stuff is worked out and there shouldn't be any data-destroying changes, then I'll probably finally give Actual an honest try! :-)
@joel-rich commented on GitHub (Oct 7, 2024):
Hey everyone, I have a suggestion/request for this item:
I understand if this adds too much complexity, but would it be feasible to have a separate "don't count this" tag for a category rather than not counting every hidden category? That would solve a couple issues with the way I'd like to use tracking budgeting.
Thanks for your consideration.
As an aside, I've very excited to switch to this budget type - I've essentially been using Actual in this way for a couple years by using a "Projected Income" budget line with negative amounts budgeted for future months, but it has been a bit clunky at times.
@psybers commented on GitHub (Oct 7, 2024):
I wonder what the purpose of 'hidden' categories is for an envelope budget? Is that really just acting more like an 'archived' category? Maybe that feature should be renamed to 'archived'? And then for tracking budgets, a new feature added called 'hidden' that hides it from the budget (but it is not archived/hidden in the UI)?
@AWare commented on GitHub (Oct 12, 2024):
I really prefer this budget type so 🥇
For hidden transactions, I just use this as a way to archive no longer relevant budgets. Such as if I need to budget for some specific thing, I can just hide that budget when it's over.
For rolled over budgets, this is useful for tracking spend that's going to be repaid- like work budgets or healthcare cash plans.
@joel-rich commented on GitHub (Oct 15, 2024):
I think calling the new tag "Tracked" or something similar would make more sense. To me, "Hidden" implies visually hidden and I'd be confused if I clicked a "Hide" button and only a total at the top of the page changed. Could have the category dropdown show "Rename / (Hide | Show or Archive | Unarchive(?)) / (Untrack | Track) / Delete"
@joel-rich commented on GitHub (Oct 23, 2024):
Has anyone had issues with this budget not filling in budgeted amounts? It seems fine if everything stays local, but doesn't seem to sync between devices properly and amounts also don't show after an export/import.
I tried digging through the code a bit last night, but I'm not at all familiar with react or the sheets/query/caching system going on so I didn't make much progress.
@youngcw commented on GitHub (Oct 23, 2024):
@joel-rich Does it still do it if you test on edge.actualbudget.org?
@joel-rich commented on GitHub (Oct 23, 2024):
@youngcw That build seems fine. Old exports still have nothing filled, but it's good if I fill the budget on edge and export then import again.
Edge is latest daily master so it'll be good next release?
@youngcw commented on GitHub (Oct 23, 2024):
Yes, everything in current edge will be in the next release.
@youngcw commented on GitHub (Nov 4, 2024):
@MatissJanis I did the needed updates to the docs page. So this is minimally ready for release.
@velotelo commented on GitHub (Nov 11, 2024):
What's the proper way to plan a budget for N months ahead with tracked option? Although I can plan each month's expenses and incomes separately, I can't find a way to link the results of previous and next months together.
Say, I'm planning my next year's budget and start with 0€ in my account on January 1st. My "projected savings" in January are 1000€, so I expect to have 1000€ in my account on January 31st.
In February I plan spending more and my "projected savings" are -1000€, so end of February I should have 0€ in my account.
How should I transfer the projected result of January to February? Currently I just copy the "projected savings" into the "starting balances" of the following month. Is that the right approach?
But then end of each month I have to manually update those "starting balances" for future months. It would be nice if that could be handled automatically like in envelope budgeting.
P.S. The envelope option doesn't work for me, since there's no way to plan my budget for next N months if I'm not able to budget in my income as well.
@MatissJanis commented on GitHub (Nov 23, 2024):
Report (tracking) budget will be released as a first party feature in v24.12.0. If there are any further feedback items and/or bug reports - please open individual issues.
Thanks to everyone that collaborated on this!