Bug 429977

Summary:	Main memo in qif import of splitted transactions get the memo value of the first splitted one instead of none
Product:	[Applications] kmymoney	Reporter:	Guy71 <bcguma2>
Component:	importer	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	REPORTED ---
Severity:	minor	CC:	adatchery, bcguma2
Priority:	NOR
Version First Reported In:	5.0.6
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	QIF import file with split transactions

Description Guy71 2020-12-03 15:04:26 UTC

SUMMARY

When importing a qif file with splitted transaction, the memo field of the global transaction get set with the memo value of the first splitted transaction instead of get assigned non value because there were no value in the global memo

STEPS TO REPRODUCE
1. Import a qif file with a splitted transaction with no memo value for the global transaction and a value for the first splitted transaction
2. 
3. 

OBSERVED RESULT

Look at the resulting transaction in KMM ledger : the global memo value is identical to the memo value of the first splitted transaction

EXPECTED RESULT

No value in the memo of the global transaction and the expected value in the memo of the first  splitted transaction

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.47.0 
Qt Version: 5.9.1

ADDITIONAL INFORMATION

Comment 1 Jack 2020-12-03 18:16:00 UTC

Are you sure that the memo is only in the one split in the QIF file?  I'm not actually aware of an import creating a split transaction, except by matching.  Can you provide a sample QIF file which demonstrated the problem?

Comment 2 Guy71 2020-12-04 09:18:22 UTC

Created attachment 133868 [details]
QIF import file with split transactions

Comment 3 Guy71 2020-12-08 10:17:22 UTC

I got this bug when importing the kind of file I uploaded, not when matching with previous transactions