[kmymoney] [Bug 395591] New: Cannot enter transaction after creating new security

[Joshua Christopher]

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

            Bug ID: 395591
           Summary: Cannot enter transaction after creating new security
           Product: kmymoney
           Version: 5.0.1
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kmymoney-devel at kde.org
          Reporter: chrisjoshtopher at gmail.com
  Target Milestone: ---

Seems very similar to: https://bugs.kde.org/show_bug.cgi?id=328280
And possibly related to: https://bugs.kde.org/show_bug.cgi?id=392477 (At least
I discovered this bug while following the workaround mentioned there).

Basically the issue is as in the title.

Reproducible: Always

Steps to Reproduce:
1. Open the ledger for an Investment Account
2. Enter a new security.
3. Complete the wizard.
4. Fill out the rest of the New Transaction form with data
5. Attempt to enter the transaction.

Actual Results:  
There is no way to enter the transaction. The Enter button is disabled and
pushing the "Enter" key on my keyboard does nothing.

The new security name is filled out in the form. If you select a different and
already existing security then try to select your new security, the new
security does not exist. While you have selected a different and already
existing security it is possible to enter the transaction.

If you go to the "Investments" page for the account you just tried to create a
new security in, the new security does show up in the list. If you then return
to the Ledger for the account, you can now select the new security and enter
transactions like normal.


Expected Results:  
You should be able to enter the transaction immediately after completing the
New Security Wizard and filling out the other necessary information in the New
Transaction Form. Switching to the Investments page and back should not be
necessary.

-- 
You are receiving this mail because:
You are the assignee for the bug.