GNOME Bugzilla – Bug 792121
Feature Request: Set action on all transactions in the Since Last Run window
Last modified: 2018-06-30 00:02:27 UTC
As I now have over 50 scheduled transactions (more to come), where most of them come at a non-precise schedule - i.e. monthly but can vary +/- n days or not happen at all - it is *really* cumbersome to go through the due ones and mark them as Postponed or Reminder. On the other hand, it is quite important not to accidentally enter one and therefore destroy the reminder. Since the ability to enter a scheduled transaction was denide, it would be a great help to be able to mark all the transactions with the same status. For example, one could "reset" all statuses to Reminder and then select only those that actuall happen for creation. Alternatively, if the Python bindings would come sooner, I'd be happy to work on this in Python as an extension.
This might not be needed in case https://bugzilla.gnome.org/show_bug.cgi?id=660375 is implemented.
When you make a feature request please remember to set the second "Importance" field to "enhancement". GnuCash doesn't invoke the python interpreter anywhere (except in the experimental Python console, but that won't do you any good here) so you can't use Python to extend GnuCash itself. The Python bindings enable you to write external programs that safely operate on a GnuCash data file/database. What's more, any changes to the behavior of the Since Last Run Dialog would have to be made directly to the dialog's code, and that's in C.
Roger that. I meant extending the scheduled transactions functionality outside GnuCash. There's already a working example (in my GnuCash Portfolio Python project) which displays a calendar view of scheduled transactions. The missing part is triggering the generation of a real transaction from a template. This would do pretty much everything I need as it would allow me to cherry-pick and enter only the transactions that were confirmed. Naturally, this could also be implemented outside GnuCash but is something I'd rather avoid. However, the pressure of now having to handle over 150 scheduled transactions in total is forcing all options back to the table. :)
I think there are a number of things that should be outside of gnc (tax tables, price db, etc). But the work in getting them out may not be worth the effort in this version of gnc, though it is obvious for some things to be outside.
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=792121. Please continue processing the bug there and please update any external references or bookmarks.