https://bugs.kde.org/show_bug.cgi?id=500902
--- Comment #8 from Mark Medoff ---
Thank you for the explanation.
When considering the wish list for modifying the memo behavior, please
reconsider how these fields were handled with the Stable version:
In the Stable version, the memo was applied to
https://bugs.kde.org/show_bug.cgi?id=500902
Jack changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=500902
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=500902
--- Comment #5 from Bug Janitor Service ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it wi
https://bugs.kde.org/show_bug.cgi?id=500902
--- Comment #4 from Mark Medoff ---
It seems that there is a difference in how the memo field is stored in
5.1.3 v 5.1.92:
When I enter a transaction with a memo in an account in *5.1.3*, the memo
is stored in the split for *both* the account and the c
https://bugs.kde.org/show_bug.cgi?id=500902
--- Comment #3 from Mark Medoff ---
It seems that there is a difference in how the memo field is stored in
5.1.3 v 5.1.92:
When I enter a transaction with a memo in an account in *5.1.3*, the
memo is stored in the split for *both* the account and the
https://bugs.kde.org/show_bug.cgi?id=500902
--- Comment #2 from Thomas Baumgart ---
I could imagine that the memo is only assigned to one split using 5.1.92 and on
both using 5.1 but wait until we receive the details from Mark. I think the
difference of the memo field in the transaction object vs
https://bugs.kde.org/show_bug.cgi?id=500902
Jack changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
