Summary: | Better handling of transaction type naming in imports | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Bob <kmymoney.qtx> |
Component: | importer | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version First Reported In: | 5.1.3 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Bob
2023-02-14 04:50:02 UTC
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. |