https://bugs.kde.org/show_bug.cgi?id=313793
--- Comment #38 from Jack <ostrof...@users.sourceforge.net> --- It also sounds good to me, certainly for new files and new categories. I'm not sure what is best for existing files where the problem is found by the consistency check. In general, I would agree to change the opening date to this new earlier value. Do you propose to change just the category with the issue, or all categories? As I remember, until now, the consistency check either simply informed the user of the issue, or, in certain cases, it just made the necessary correction. In this case would it make sense to offer the user a choice: 1) do nothing and let the user fix the file manually, 2) move the date of the transaction (that is the current option, right?) 3) change the opening date of this category, or 4) change the opening date of ALL categories. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
