https://bugs.kde.org/show_bug.cgi?id=521431

            Bug ID: 521431
           Summary: UI should limit moving transaction to only of Category
                    or Account type.
    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
While the UI makes an effort to ease users into the concept of double-entry
bookkeeping by introducing the concept of Expense/Income Categories and
Asset/Liability Accounts, it is still possible to assign a transaction to any
type of account when in edit mode.
However, the UI also artificially enforces that split when not necessary, e.g.
when trying to move a transaction between Category and Asset/Liability type.
This creates unnecessary friction as there is no underlying technical reason to
prevent the move—especially since the user can bypass this restriction simply
by editing the transaction manually, adding to confusion.

Additionally, the UI doesn't do a good job at explaining why a particular
account might be missing from the list, which happens if there's a
currency/security mismatch.

STEPS TO REPRODUCE
1. In any account, find a transaction that is assigned to an Expense/Income
category
2. Right click it, choose Move option

OBSERVED RESULT
You can only move that transaction to another Expense/Income category. 

EXPECTED RESULT
It should be possible to move that transaction to any type of account, be it
Expense, Income, Investment, Liability, Asset or Equity, provided that the
target account matches the currency. Additionally, if currency mismatch is
detected between the transaction and an account, it should be disabled with a
tooltip, not removed from the list entirely.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to