Bug 299910 - Income and Expenses Forecast Report is wrong when scheduled transactions are included
Summary: Income and Expenses Forecast Report is wrong when scheduled transactions are ...
Status: RESOLVED DUPLICATE of bug 295239
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.2
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-12 21:22 UTC by sasavilic
Modified: 2014-07-28 15:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sasavilic 2012-05-12 21:22:17 UTC
After creating scheduled transaction (which runs once per day) and generating forecast report of income and expenses, the report has wrong values.

I have a daily expense that it is for example 8 EUR. But in forecast report I see following results:
May: 8, Jun: 8, Aug: 8, Sep: 8, Oct: 8, Nov: 8, Dec: 248, Total: 304

Reproducible: Always

Steps to Reproduce:
1. Create account if you don't have one
2. Create category under expenses
3. Open dialog for creating scheduled transaction
4. Enter some name
5. By Frequency, choose Day
6. Choose your account that you have created
7. Choose category that you have created
8. Enter amount (e.g. 8)
9. Press OK
10. Go to reports
11. Open Forecast -> Income and Expenses Forecast This Year
12. Press Configure
13. Go to tab Rows/Columns
14. Check "Include scheduled transactions"
15. Press Ok
16. Generated report should create wrong values
Actual Results:  
Jan: 0
Feb: 0
Mar: 0
Apr: 0
May: 8
Jun: 8
Jul: 8
Sep: 8
Oct: 8
Nov: 8
Dec: 248

Expected Results:  
Jan: 0
Feb: 0
Mar: 0
Apr: 0
May: 152
Jun: 240
Jul: 248
Sep: 240
Oct: 248
Nov: 240
Dec: 248

Today is 12th May 2012. This date is important because of generated report. 

I have KDE with following language settings:
* Language: English
* Country: Austria
Comment 1 Cristian Oneț 2014-07-28 15:10:01 UTC

*** This bug has been marked as a duplicate of bug 295239 ***