SUMMARY *** It's annoying that apparently the phrasing of transactions must be matched exactly when manually importing a CSV file. 'Dividend Reinvestment' is not the same as 'Reinvest Dividend' and thus import fails requiring a manual editing of every transaction in the import file. It would be great if a popup could be implemented that would allow the user to specify/select what the transaction type is from the KMM display list and then remember that for the duration of the import or perhaps longer. Given the decision not to support cash in an investment account which is contrary to almost all investment accounts I have, intelligent importing of mixed transactions from those accounts would be very nice to support. Since the program knows of the association of investment and brokerage accounts from when they were created, give the importer the ability to direct a line item to either the investment or brokerage account. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT import fails EXPECTED RESULT user can map the import file transaction types to what the program has defined, greatly decreasing user frustration with the import process SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
When I use the csv importer for an investment account, if it does not recognize the transaction type, it does ask, and it does remember the match (at least for the rest of that import - I don't recall trying a repeat import.) I'll have to test explicitly in 5.1 (I'm mainly using master) but I don't think they should differ in this. Does this really not happen for you? What error message do you get? I also know that OFX import does import cash transactions to the associated brokerage account, but have not explicitly tested this for CSV import. (It's not on my list to test.)
I have also confirmed that if you assign an unkown transaction type to a known one, the csv importer does remember that matching for a later import using the same template.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Changed into a wish list entry and re-opened it.