Bug 408349 - Closed Accounts Showing in Drop Down
Summary: Closed Accounts Showing in Drop Down
Status: RESOLVED DUPLICATE of bug 407021
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.4
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-05 15:23 UTC by Robert Blackwell
Modified: 2019-06-05 16:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Closed Accounts (21.56 KB, image/jpeg)
2019-06-05 15:23 UTC, Robert Blackwell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Blackwell 2019-06-05 15:23:55 UTC
Created attachment 120600 [details]
Closed Accounts

SUMMARY

Using KMyMoney Version 5.0.4-52a838f73

Closed accounts are listed in the Drop Down menu on the Ledger tab.

I needed to check data in a closed account so I switched the view to "Show Hidden Accounts. Upon reverting back to the former view, closed accounts remained in the Drop Down menu of the Ledger screen. These accounts do not show up in the Accounts list.

STEPS TO REPRODUCE
1. At the Configure KMyMoney window select the General category
2. Change to the Filter Tab
3. Uncheck "Do not show closed accounts".
4. Apply the setting and close the window
4. Perform data query on closed account
5. Return to the Configure KMyMoney window - General category
6. Change to the Filter Tab
7. Check "Do not show closed accounts".
8. Apply the setting and close the window

OBSERVED RESULT
Closed accounts remained visible in drop down menu of Ledger Screen

EXPECTED RESULT

Closed accounts would no longer appear in drop down menu on Ledger screen


SOFTWARE/OS VERSIONS
Windows: 10 Pro build 1809
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Screen shots attached
Comment 1 Thomas Baumgart 2019-06-05 16:12:51 UTC

*** This bug has been marked as a duplicate of bug 407021 ***