Bug 503383

Summary:	Quick Fix: Extend Budget Copy Limit from 2029 to 2031
Product:	[Applications] kmymoney	Reporter:	pierremaille
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	wishlist
Priority:	NOR
Version First Reported In:	5.1.3
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot of forecast forecast

Description pierremaille 2025-04-26 11:12:27 UTC

Hello,

I would like to suggest a small but impactful improvement regarding the budget feature in KMyMoney.

Currently, when creating a budget based on forecast for the current year, KMyMoney pulls data from past transactions to define the budget for previous months. While this works well for future months, it doesn't suit scenarios where a budget strictly based on scheduled transactions is needed.

A practical workaround I found is to generate a forecast budget for the following year (e.g., 2026 while we are in 2025) and then manually set the budget year back to 2025. This method effectively creates a budget driven by scheduled transactions only.

However, this approach introduces a minor issue: the alignment of weekdays. For accurate planning, it's preferable to use a year where the weekdays match the target year. In this case, 2031 would be ideal since it shares the same weekday pattern as 2025. Unfortunately, KMyMoney currently limits the budget copy function to the year 2029.

If you could extend this limit to allow copying budgets up to at least 2031, it would perfectly resolve this situation. It seems like a quick adjustment that would greatly enhance flexibility for users relying on scheduled transactions to structure their budgets.

Thank you for considering this improvement.

Comment 1 Thomas Baumgart 2025-04-26 13:43:39 UTC

I somehow don't understand your use case (not the workaround but the original one). The method used to create a budget (historic values or scheduled/future transactions) is controlled by the setting of the forecast view. Did you play with that setting?

The forecast code has been developed about 15 years ago by a developer who is not on the team anymore and the budget logic just makes use of it. From what I remember, the selection of the method is an exclusive or, so I don't understand how you could see both methods used when you create the budget. Again, I have no clue how this works internally.

The current development version does not have a limit on the year, so you may want to try that. Check https://kmymoney.org/windows.html for instructions.

Comment 2 pierremaille 2025-04-27 01:04:10 UTC

Created attachment 180694 [details]
Screenshot of forecast

Comment 3 pierremaille 2025-04-27 01:06:21 UTC

Created attachment 180695 [details]
forecast

Comment 4 pierremaille 2025-04-27 01:10:55 UTC

Hello,
Thank you very much for the quick response. I was referring to the default forecast in the Budgets section.
I populate the budget based on scheduled transactions. As previously mentioned, when using this method, the budgets for previous months are based on actual transactions instead of scheduled transactions.

Comment 5 Bug Janitor Service 2025-05-12 03:46:55 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2025-05-27 03:47:34 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.