github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 04:49:45 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #4079] [Feature] Add Budget from Same Month Last Year #27527

New Issue
Closed
opened 2026-04-18 04:05:51 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 04:05:51 -05:00
Owner
Copy Link

Originally created by @itthipho1 on GitHub (Jan 3, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4079

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

For users with seasonal or cyclical spending patterns, it is difficult to set budgets accurately using the current options (copying last month's budget or setting averages). Many expenses—like holidays, utility bills, and vacations—follow yearly patterns. Without the ability to set budgets based on the same month from the previous year, users must manually reference past data, which can be time-consuming and prone to error.

Describe your ideal solution to this problem

Add a new option in the budget-setting menu to "Copy budget from the same month last year." This option would use data from the same month of the prior year to set the current month’s budget. It should work alongside existing options like "Copy last month’s budget" or "Set to yearly average."

For example:
If you’re budgeting for January 2025, the "Same Month Last Year" option would pull the budgeted amounts from January 2024.

Teaching and learning

To make this feature intuitive and accessible:

  1. Add documentation or a tooltip explaining how the "Same Month Last Year" feature works.
  2. Provide a quick note in the budget-setting interface that shows what month and year the data is pulled from.
  3. Add an optional confirmation step before applying this feature, so users can review the values being copied.
Originally created by @itthipho1 on GitHub (Jan 3, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4079 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? For users with seasonal or cyclical spending patterns, it is difficult to set budgets accurately using the current options (copying last month's budget or setting averages). Many expenses—like holidays, utility bills, and vacations—follow yearly patterns. Without the ability to set budgets based on the same month from the previous year, users must manually reference past data, which can be time-consuming and prone to error. ### Describe your ideal solution to this problem Add a new option in the budget-setting menu to "Copy budget from the same month last year." This option would use data from the same month of the prior year to set the current month’s budget. It should work alongside existing options like "Copy last month’s budget" or "Set to yearly average." For example: If you’re budgeting for January 2025, the "Same Month Last Year" option would pull the budgeted amounts from January 2024. ### Teaching and learning To make this feature intuitive and accessible: 1. Add documentation or a tooltip explaining how the "Same Month Last Year" feature works. 2. Provide a quick note in the budget-setting interface that shows what month and year the data is pulled from. 3. Add an optional confirmation step before applying this feature, so users can review the values being copied.
GiteaMirror added the feature label 2026-04-18 04:05:51 -05:00
GiteaMirror commented 2026-04-18 04:05:53 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 3, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 👍!

<!-- gh-comment-id:2568690737 --> @github-actions[bot] commented on GitHub (Jan 3, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-18 04:05:53 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 3, 2025):

You can use the copy template to do this

<!-- gh-comment-id:2569365114 --> @youngcw commented on GitHub (Jan 3, 2025): You can use the copy template to do this
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 feature
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#27527
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?