https://bugs.kde.org/show_bug.cgi?id=521407
Bug ID: 521407
Summary: Impossible to convert transaction into a "regular" one
after importer false-positively prefills using past
security transaction
Classification: Applications
Product: kmymoney
Version First 5.2.2
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: ux-ui
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
When importing transactions, using e.g. CSV importer, it is possible that a
transaction gets prefilled using a previous transaction of security type. If
that happens, it is impossible to convert that transaction back into a regular
one.
This is a UI issue, after all. When *not* in edit mode, a security transaction
is shown as assigned to a Category (which itself is a security account).
However, when entering Edit mode, one can change the Activity type and the
Security name, but it is impossible to make it a regular transaction.
As a result, one has to delete that transaction and enter all of the details by
hand.
STEPS TO REPRODUCE
1. Import a transaction that matches a Payee and Amount of a past transaction
of security type
2. An imported transaction should be automatically prefilled with that
transaction's details
OBSERVED RESULT
It is impossible to edit that transaction and assign it to a regular,
non-security type category.
EXPECTED RESULT
It should be possible to change the category to any type, not limited to
Securities only.
Current UI is inconsistent: in view mode, it displays a Category field,
meanwhile in Edit mode it displays a Security field.
--
You are receiving this mail because:
You are watching all bug changes.
