[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 --- Comment #4 from Martin Steigerwald --- (In reply to Jack from comment #3) > If you provide a suggested improvement to the manual, I'll be glad to > consider including it. You could also suggest a change to the actual > wording included on the dialog itself, but those are constrained by > real-estate > and programmer time. […] I reviewed the documentation and I think it is good. I did not know the CSV importer was documented (until I found a bug report about this by accident today). I think the GUI should make it obvious that you can add mutiple fields to memo. Usually ways would be to have a list were the user can select mutiple items via shift or ctrl + mouse click or to have a check mark for each field and the user can select mutiple ones. Also I´d probably allow to add any field there, no matter whether it is used elsewhere or not, in any order. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net Severity|normal |wishlist --- Comment #3 from Jack --- If you provide a suggested improvement to the manual, I'll be glad to consider including it. You could also suggest a change to the actual behavior or to wording included on the dialog itself, but those are constrained by real-estate and programmer time. However, I'm switching this to wish-list, so it can server as a reminder. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 Martin Steigerwald changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Martin Steigerwald --- (In reply to Jack from comment #1) > If you set the column for the PAYEE field first, then you can set the same > column for inclusion in the MEMO field. The interface is not as clear as it > could be about what happens, but it does work. You can also include > multiple columns in the MEMO field, but they need to be selected for any > other purpose first, and then assign them to the MEMO field. Whoa. This works. It is very well hidden tough. I think I let this bug open for now, as I think this is an usability issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 --- Comment #1 from Jack --- If you set the column for the PAYEE field first, then you can set the same column for inclusion in the MEMO field. The interface is not as clear as it could be about what happens, but it does work. You can also include multiple columns in the MEMO field, but they need to be selected for any other purpose first, and then assign them to the MEMO field. If this still doesn't work for you, you can create a sample CSV where you have changed all the actual names and values, -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393441] CSV import: description field original text not saved permanently
https://bugs.kde.org/show_bug.cgi?id=393441 Martin Steigerwald changed: What|Removed |Added Summary|CSV import: description not |CSV import: description |saved permanently |field original text not ||saved permanently -- You are receiving this mail because: You are watching all bug changes.
