Bug 297873

Summary: Budget year not the same as specified fiscal year
Product: [Applications] kmymoney Reporter: mike <michael.ian.bennet>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED FIXED    
Severity: wishlist CC: asoliverez, nicolas.puiroux, spaldingdavid1947
Priority: NOR    
Version: git (master)   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In: 5.0
Sentry Crash Report:

Description mike 2012-04-10 21:52:10 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.152 Safari/535.19
Build Identifier: 

I configured the fiscal year to start 1 March. However, the budget year stays as calendar year starting January.

Reproducible: Always

Steps to Reproduce:
1.Configure fiscal year to start 1 March
2.Create new budget and select fiscal year
3.Enter budget figures
Actual Results:  
New budget months start January, but should start March based on configured fiscal year
Budget report only shows figures within a calendar year even when I customise the dates to run 1 March 2012 to 28 Feb 2013

Expected Results:  
I expected to see months starting from March and ending February (following calendar year)
Comment 1 Alvaro Soliverez 2012-04-28 23:30:34 UTC
That's how it works at the moment, even if expected different.

Moving to wishlist.
Comment 2 wojnilowicz 2017-04-25 18:58:14 UTC
*** Bug 379124 has been marked as a duplicate of this bug. ***
Comment 3 wojnilowicz 2017-04-25 18:58:44 UTC
Git commit 84112ff06c9ae7376c8bc4516611fbe43eea0fa5 by Łukasz Wojniłowicz.
Committed on 25/04/2017 at 18:24.
Pushed by wojnilowicz into branch 'master'.

Respect fiscal year's start setting for budgets
Related: bug 337836
FIXED-IN:5.0

Signed-off-by: Łukasz Wojniłowicz <lukasz.wojnilowicz@gmail.com>

M  +4    -4    kmymoney/kmymoney.cpp
M  +7    -3    kmymoney/views/kbudgetview.cpp
M  +4    -3    kmymoney/widgets/kbudgetvalues.cpp

https://commits.kde.org/kmymoney/84112ff06c9ae7376c8bc4516611fbe43eea0fa5
Comment 4 wojnilowicz 2017-05-02 05:54:03 UTC
*** Bug 315789 has been marked as a duplicate of this bug. ***