Bug 360662

Summary: Deposits or payments scheduled on first of month do not show up in budgeted vs actual report
Product: [Applications] kmymoney Reporter: Ann <msaspears>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED FIXED    
Severity: normal CC: ralf.habacker
Priority: NOR    
Version: 4.6.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: attachment-9504-0.html

Description Ann 2016-03-17 13:33:33 UTC
Version 4.6.4 Using KDE Development Platform 4.13.3
Deposits or payments scheduled on first of month does not show up in budgeted vs actual report. The values set in the budget are included in the "budgeted" part of the report. The values for the first of the month deposits or payments do not show up in the "actual" part of the report. This occurs, of course, when choosing to include scheduled transactions in the report.  If I set the date to the 2nd of the month the deposit or payment shows up in the report. Its a problem when I have recurring deposits (say, every week or two weeks) and one of the dates happens to fall on the first of the month. That deposit then does not show up in the report. This appears to be a problem for all years and months.


Reproducible: Always

Steps to Reproduce:
1. Set up a deposit or payment in the scheduled transactions on the first of any month.
2. Create budget values if you wish, although that is not where the problem occurs
3. Create a budgeted vs actual report. Under configure report, then under rows and columns, click on " include scheduled transactions"
4. Modify date to include future transactions.


Actual Results:  
The first of the month deposits and payments do not show up in the budgeted vs actual report under the "actual" column. This does not appear to be happening when I use other reports with "actual" values including scheduled transactions 

Expected Results:  
I expected correct numbers based on my scheduled transactions. This skewing forecast reports that I use. 

I can't think of anything else that might be pertinent.
Comment 1 Justin Zobel 2022-11-30 05:28:15 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Ann 2022-12-01 07:58:24 UTC
Created attachment 154184 [details]
attachment-9504-0.html

This is no longer an issue. Thanks for fixing.

Ann Spears

On Wed, Nov 30, 2022 at 12:28 AM Justin Zobel <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=360662
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Thomas Baumgart 2022-12-02 07:01:19 UTC
As per previous comment