mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 04:02:38 -05:00
[Feature] "Copy last month's budget": ignore any values already set for that month #382
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#382
Reference in New Issue
Block 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 @bstritesky on GitHub (May 1, 2023).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I sometimes vary budgeted amounts for categories month-to-month, manually populating those values in budgeted amounts for the current month prior to performing the copy action. Currently, the "Copy last month's budget" action pulls all budgeted amounts from the last month, regardless of what I have manually set for the current month.
Describe your ideal solution to this problem
It would be nice if the "Copy last month's budget" action would respect any values I have already set for the current month, and only pull budget amounts from the previous month if the current month has no budget value set.
Teaching and learning
No response
@github-actions[bot] commented on GitHub (May 1, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!
@glancep commented on GitHub (Jan 2, 2024):
+1. I would love this feature. Coming from YNAB4, this is exactly how it worked. Our workflow is very similar as described above--if we need to make a one-off change, we'll manually enter the "go-forward" budget amount into next month's as a reminder of what it should be. When we went to budget that next month, we copied from the prior month and almost missed that it overwrote our manually entered value.