GnuCash
Contact   Instructions
Bug 796990 - Budget : Empty Accounts Are Missing Every Time Budget is Opened
Summary: Budget : Empty Accounts Are Missing Every Time Budget is Opened
Status: RESOLVED DUPLICATE of bug 796965
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Budgets (show other bugs)
Version: 3.3
Hardware: PC Windows
: High major
Target Milestone: ---
Assignee: core
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-23 20:28 EST by Alex Mak
Modified: 2019-02-09 02:52 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Alex Mak 2018-12-23 20:28:46 EST 
Newly created account and account with zero transaction cannot be shown in Budget

1. Action --> New Budget
2. Open Budget
3. Account without transaction is not shown in Budget page
4. Create new account
5. Open budget
6. Newly account also is not shown in Budget page
Comment 1 Robert Chapin 2019-02-08 17:42:23 EST 
I think I am having this same problem in 3.4.

I just started updating my 2019 budget and several accounts are completely missing from the budget editor.  😢
Comment 2 Robert Chapin 2019-02-08 17:47:22 EST 
Well, aside from looking very buggy, this can be fixed as follows:

1. Open a budget.
2. Click the View menu.
3. Click Filter By...
4. Click the Other tab.
5. Click Show unused accounts.
6. Click OK.
Comment 3 Robert Chapin 2019-02-08 18:12:11 EST 
Changing back to high priority again.

This filter has to be reset EVERY TIME the budget it opened.  😣
Comment 4 Robert Chapin 2019-02-08 18:42:27 EST 
Additional symptom:

If a budget entry is added to an "empty" account using the steps I posted above, then the next time the budget is opened those budget entries are also missing unless the filter is manually adjusted again.
Comment 5 Geert Janssens 2019-02-09 02:52:30 EST 
Thank you for your report. I'm happy to announce this has been fixed for the upcoming 3.5 release.

*** This bug has been marked as a duplicate of bug 796965 ***
Note You need to log in before you can comment on or make changes to this bug.