GNOME Bugzilla – Bug 791993
Report for tracking budgets
Last modified: 2018-06-30 00:02:10 UTC
Created attachment 366029 [details] [review] Report to be added to gnucash This report exists to aide in envelope accounting. The standard practice has been to create scheduled transactions that add the budget amount to the expense accounts. However this doesn't let me leverage the other budget reports. So I created this report that is essentially an account register for the expense account with the budget values added in like the scheduled transactions would, except the expense account is still accurate for use with the budget reports.
Comment on attachment 366029 [details] [review] Report to be added to gnucash Sorry, we're not able to accept this patch. First of all, don't write patches against tarball releases. Clone the repository and write your patches against the HEAD of the appropriate branch. Second, we don't accept new features on the maintenance branch, though we will may change that policy at some point after the release of 3.0; in any case the 2.6 branch has only its end-of-life release left and new features on it would be silly. Third, it's incomplete and not correctly prepared. Please see https://wiki.gnucash.org/wiki/Development#Submitting_Patches for instructions on how to prepare patches. For it to be a complete patch it also needs code adding it to the reports menu somewhere (Reports>Budget seems reasonable) as well as build system changes (to both CMakeLists.txt and Makefile.am in the appropriate directory, probably gnucash/report/standard-reports). Unfortunately we went to feature freeze on the unstable branch that we'll release as 3.0 in another 2-3 months so we can't accept a reworked version of your patch for that, either. I suggest that you redo your patch against the "master" branch for inclusion in 4.0... but wait a couple of weeks before you start as we're working on changing some of the internal scheme date-handling code and you'll want to use the new version rather than the old. If we decide to add features to 3.0 during its maintenance lifetime new reports will certainly be at the top of the list for consideration, so I suggest that you subscribe to the developer's mailing list.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=791993. Please update any external references or bookmarks.