https://bugs.kde.org/show_bug.cgi?id=503383
Bug ID: 503383
Summary: Quick Fix: Extend Budget Copy Limit from 2029 to 2031
Classification: Applications
Product: kmymoney
Version: 5.1.3
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: kmymoney-devel@kde.org
Reporter: pierremai...@gmail.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
