github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #4877] [CLOSED] fix(template): update up to logic to handle future months #5639

New Issue
Closed
opened 2026-02-28 21:15:52 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:15:52 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4877
Author: @kopach
Created: 4/22/2025
Status: ❌ Closed

Base: master ← Head: future-up-to

📝 Commits (2)

  • cf8e1cf fix(template): update up to logic to handle future months
  • 107bd5e chore: update release notes

📊 Changes

2 files changed (+13 additions, -0 deletions)

View changed files

📝 packages/loot-core/src/server/budget/categoryTemplate.ts (+7 -0)
➕ upcoming-release-notes/4877.md (+6 -0)

📄 Description

Fixes #template up to <amount> logic to ignore future month balances when applying templates, enabling accurate forward budgeting as discussed in: https://discord.com/channels/937901803608096828/1364159049553281109

Context

Previously, #template up to would incorrectly consider the category balance when budgeting future months — causing potential underfunding when previous months would be used up fully.

Fix

This PR adjusts the behavior of #template up to:

  • Current month budgeting: no changes, still respects the actual balance (for refill behavior).
  • Future months budgeting: ignores balance entirely, assuming it to be 0, enabling consistent monthly assignments regardless of rollovers.

This behavior now matches YNAB’s “Refill up to” approach and allows users to simulate a worst-case scenario of no carry over — essential forward budgeting, aka financial cushion

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/4877 **Author:** [@kopach](https://github.com/kopach) **Created:** 4/22/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `future-up-to` --- ### 📝 Commits (2) - [`cf8e1cf`](https://github.com/actualbudget/actual/commit/cf8e1cfc4fce309694baa4781fcfb629f71ffa17) fix(template): update `up to` logic to handle future months - [`107bd5e`](https://github.com/actualbudget/actual/commit/107bd5e0af64fa3a34ce4a8ad159db4fcd993cd2) chore: update release notes ### 📊 Changes **2 files changed** (+13 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/src/server/budget/categoryTemplate.ts` (+7 -0) ➕ `upcoming-release-notes/4877.md` (+6 -0) </details> ### 📄 Description Fixes `#template up to <amount>` logic to ignore future month balances when applying templates, enabling accurate forward budgeting as discussed in: https://discord.com/channels/937901803608096828/1364159049553281109 **Context** Previously, `#template up to` would incorrectly consider the category balance when budgeting future months — causing potential underfunding when previous months would be used up fully. **Fix** This PR adjusts the behavior of `#template up to`: - **Current month budgeting**: no changes, still respects the actual balance (for refill behavior). - **Future months budgeting**: ignores balance entirely, assuming it to be 0, enabling consistent monthly assignments regardless of rollovers. This behavior now matches YNAB’s **“Refill up to”** approach and allows users to simulate a worst-case scenario of no carry over — essential forward budgeting, aka **financial cushion** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:15:52 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub 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
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#5639
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?