[kmymoney] [Bug 185570] changing account type not possible

https://bugs.kde.org/show_bug.cgi?id=185570 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[kmymoney] [Bug 178906] no customer identifiation number for banks

https://bugs.kde.org/show_bug.cgi?id=178906 Jack changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because:

[kmymoney] [Bug 178906] no customer identifiation number for banks

https://bugs.kde.org/show_bug.cgi?id=178906 Jack changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NE

[kmymoney] [Bug 225550] Import does not set detail field correctly

https://bugs.kde.org/show_bug.cgi?id=225550 Jack changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[kmymoney] [Bug 283783] KMyMoney does not show scheduled transactions in the ledger with a primary sort key different than the post date

https://bugs.kde.org/show_bug.cgi?id=283783 --- Comment #5 from Jack --- While 5.1 seems to still only show future scheduled transactions if the sort order is primary date ascending, current master shows them for any sort order (that I have tested.) They are shown very dim, so they are definitel

[kmymoney] [Bug 463015] Inactive Payee

https://bugs.kde.org/show_bug.cgi?id=463015 --- Comment #2 from Jack --- You are correct that there is no current way to tell KMM not to allow any new transaction for a given Payee, so this is valid wishlist request. At minimum, marking a Payee as inactive would remove that Payee from any dropdo

[kmymoney] [Bug 463246] Importing CSV's with double-sets of quotes ("") splits the field

https://bugs.kde.org/show_bug.cgi?id=463246 --- Comment #3 from Jack --- It really would make it easier if you provide a sample csv file, even if it's only a header and one data row. It may be obvious to you what is wrong, but debugging to find exactly where in the code the problem occurs is eas

[kmymoney] [Bug 377869] when adding a second entry w\o payer/receiver it substitute from previous entry

https://bugs.kde.org/show_bug.cgi?id=377869 Jack changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kmymoney] [Bug 463246] Importing CSV's with double-sets of quotes ("") splits the field

https://bugs.kde.org/show_bug.cgi?id=463246 --- Comment #2 from m...@eisgr.com --- https://www.rfc-editor.org/rfc/rfc4180 ``` 2. Definition of the CSV Format ... 7. If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by precedin

[kmymoney] [Bug 385900] Report generates different sum values compared to the stable version

https://bugs.kde.org/show_bug.cgi?id=385900 Jack changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO

[kmymoney] [Bug 463246] Importing CSV's with double-sets of quotes ("") splits the field

https://bugs.kde.org/show_bug.cgi?id=463246 alx.ku...@gmail.com changed: What|Removed |Added CC||alx.ku...@gmail.com --- Comment #1 from al

[kmymoney] [Bug 400465] Imported transactions are not matched against reconciled transactions

https://bugs.kde.org/show_bug.cgi?id=400465 --- Comment #5 from Jack --- Given the original report was for QIF files, I'm not going to change the status, and will let this one get closed if the OP doesn't respond. OFX duplicate detection generally relies on a unique transaction ID provided by th

[kmymoney] [Bug 463246] New: Importing CSV's with double-sets of quotes ("") splits the field

https://bugs.kde.org/show_bug.cgi?id=463246 Bug ID: 463246 Summary: Importing CSV's with double-sets of quotes ("") splits the field Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other

[kmymoney] [Bug 400465] Imported transactions are not matched against reconciled transactions

https://bugs.kde.org/show_bug.cgi?id=400465 Phillip Vuchetich changed: What|Removed |Added Platform|Other |Microsoft Windows CC|

Re: Error.

Alonso, On Montag, 19. Dezember 2022 13:35:30 CET Alonso González Chaves via KMyMoney-devel wrote: > Hello. > When executing the Transactions Report of an account by default, the report > comes out fine, however, when you want to do something in the configuration > of that report, an error app