GNOME Bugzilla – Bug 465602
Paid bills become unpaid after closing books
Last modified: 2018-06-29 21:45:31 UTC
Steps to reproduce: 1. Have a file with unpaid bills 2. Close books 3. Save 4. Close down gnuCash 5. Reopen file 6. View bills via vendor look up. Bills should remain paid after books have been closed. It would also be necessary to have a tool to mark the bills paid. Closing again and re-entering new accounting information after close off would just be too much.
unpaid means the paid column in the list of bills becomes unticked
Honestly, closing the books isn't supported, and should have been disabled before 2.2.0 was finally released. I'll make sure it's disabled before 2.2.1.
(setting milestone to remind people to disable "Close Books" for 2.2.1)
Apologies there's a typo. Bug Report Line 1 should read: 1. Have file with paid bills. 2. .......
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 458434 ***
I don't think this bug is a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=458434 458434. For one, to a layperson (who snipes from the slide lines:-P) there are no similarities with the bug description summary. But more importantly, shutting down the close books feature is a mere remedy for this issue. I understand that work on this feature is not complete but, with the assumption that closing books will be a permanent feature, the resolution of this issue may or may not be fixed when close books is re-enabled. This bug seems to have a relationship with http://bugzilla.gnome.org/show_bug.cgi?id=106383 where it is a blocker. I urge you to reconsider the resolution of this bug and reinstate it as well as creating some sort of relationship with http://bugzilla.gnome.org/show_bug.cgi?id=106383.
True, removing a non-working feature that has a side-effect is indeed not fixing the side-effect.. But the feature isn't complete, so keeping around a bug report about of side-effect of a non-working feature is just adding garbage to bugzilla. Once we feel the book-closing feature is complete, THEN if it happens we can file a bug report. But until this, this report has no bearing on the existing application.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=465602. Please update any external references or bookmarks.