Summary: | Cannot create transaction if I changed in the past the account's opening date | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Francescu Garoby <windu.2b> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | flywire0, gilbertoca, windu.2b |
Priority: | NOR | ||
Version: | git (master) | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Francescu Garoby
2015-05-08 16:19:40 UTC
(In reply to Francescu Garoby from comment #0) > I opened a new account the 2015/07/23, but created my KMyMoney file today > (2015/05/08). I changed the account's opening date to 2015/07/23, but it > didn't change the categories opening date (still 2015/05/08). So I can't > create a transaction between the account's opening date and today. > If I change the category's opening date to 2014/07/23 (like the account's > opening date), I can create a transaction. > > Reproducible: Always > > Steps to Reproduce: > 1. create a new account > 2. change its opening date in the past > 3. create a transaction with a date between the account's opening date and > today. > > Actual Results: > * An error message appears : "Cannot enter transaction with postdate prior > to account's opening date." > * the "Enter" button is desactivated > > Expected Results: > I can create a transaction > > The error message is wrong : the transaction is not prior to the account's > opening date but prior the category's opening date. > > Why the categories have an opening date ? Is it really useful ? I think the > categories shouldn't have an opening date, by default. > But if necessary, the user can add an opening date (posterior to the > account's opening date, of course). Please take a look at this discussion https://bugs.kde.org/show_bug.cgi?id=313793#c25 I also think this is regression and the user should make the decision whether it is automatic or not. *** This bug has been marked as a duplicate of bug 347400 *** *** No. Not a duplicate of bug 347400 *** and a better description. *** Not fixed in V4.7.2 on Win7-32 *** |