https://bugs.kde.org/show_bug.cgi?id=351511
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ostroffjh@users.sourceforge
| |.net
--- Comment #2 from Jack <ostrof...@users.sourceforge.net> ---
I agree with Allan it's not a bug, although it might be an unintended
consequence of the design. However, I think it's important to know exactly how
this happened. If you can provide a minimal test case, it would help. In
particular, if you have a QIF file with the two transactions, one for "Pool"
and one for "Liverpool" and neither payee exists in the kmy file, when you
import the QIF, does it create one or two payees? If both "Pool" and
"Liverpool" payees exist, and you import another QIF which includes both
(different transactions, so we don't conflate payee matching with transaction
matching) do they get assigned to the correct payees or both to "Pool"?
Also, if the "Pool" payee was automatically created by the first import, what
are the payee matching settings for that payee?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
