Bug 327265 - KMyMoney reports do not accept data periods input
Summary: KMyMoney reports do not accept data periods input
Status: RESOLVED DUPLICATE of bug 312676
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-07 09:12 UTC by Dr.Edgar Alwers
Modified: 2014-07-29 10:06 UTC (History)
2 users (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 Dr.Edgar Alwers 2013-11-07 09:12:47 UTC
if I generate a report, let me say, about some expenses during the current year, I always get 
the  report on all the transactions. No matter what I do, the desired data period is always ignored. My KMM does not crash.  Example: I just made  a copy of a report ( fuel expenses for my car during the current fiscal year ). The title changed to "01.01.2013 through 31.12.2013" but the report did not change and starts with the 09.06.2012, the start date of my account. I am using KMM 4.6.4 under KDE 4.10.2, Linux from Scratch, Kernel 3.8.5 and MySQL 5.6.11.

Reproducible: Always

Steps to Reproduce:
1. I try to generate a report, e.g. expenses during a  certain period of time
2. report is generated, but for all expenses, time period is not considered
3.
Actual Results:  
Report is always the same, disregarding the desired time period.  Fields on the report can be selected, the program works here correctly

Expected Results:  
Reports generated for the data period I enter

I cannot say if the problem persists not using a database MySQL
Comment 1 Fernando Vilas 2013-11-08 03:28:41 UTC
I just checked on the git-master and was able to get a report of income versus expenses from 2012 by changing the dates on the current year report to last year's. I am using a different database, but not the xml backend.
Comment 2 Cristian Oneț 2014-07-29 10:06:04 UTC

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