| Summary: | Unexpected behavior when entering a schedule that has a changed amount and a transaction date later than the due date | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Cristian Oneț <onet.cristian> |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | git (master) | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Use this file to go trough the steps to reproduce this bug | ||
Git commit 711db3f349a34aab4e41a7609c71e7f626cd8605 by Cristian Oneț. Committed on 26/12/2011 at 12:51. Pushed by conet into branch 'master'. When changing the transaction of a schedule keep the original due date. Related: bug 289834 M +3 -1 kmymoney/kmymoney.cpp http://commits.kde.org/kmymoney/711db3f349a34aab4e41a7609c71e7f626cd8605 Git commit d7f91828b2f566cdb4da6bc378a17cdce14f45e6 by Cristian Oneț. Committed on 26/12/2011 at 12:51. Pushed by conet into branch '4.6'. When changing the transaction of a schedule keep the original due date. Related: bug 289834 M +3 -1 kmymoney/kmymoney.cpp http://commits.kde.org/kmymoney/d7f91828b2f566cdb4da6bc378a17cdce14f45e6 |
Created attachment 67113 [details] Use this file to go trough the steps to reproduce this bug Version: git master (using KDE 4.7.3) OS: Linux When entering a schedule that: 1. Has some transaction data changed like the amount for example 2. The date was changed to be after the due date 3. The user selects 'Set all further occurrences in this schedule to be these values' while only the changed amount is displayed After a schedule in the above conditions is entered the next dues date of the schedule is incorrectly set to the payment date of the transaction that was just entered. Reproducible: Didn't try Steps to Reproduce: Use the attached file and enter schedule 'Salary' which is a monthly schedule due on '25.12.2011'. 1. Changed the amount to 110 2. Change the transaction date to '26.12.2011' 3. Enter the schedule and select 'Set all further occurrences in this schedule to be these values' Actual Results: The transaction is entered and the next due date of the schedule is set to '26.12.2011' which is wrong since we've just entered the transaction for that date. Expected Results: The transaction is entered and the next due date of the schedule is set to '25.01.2011' just like when we don't select 'Set all further occurrences in this schedule to be these values' OS: Linux (x86_64) release 3.0.6-gentoo Compiler: x86_64-pc-linux-gnu-gcc