GNOME Bugzilla – Bug 600374
Implements editable transaction field in the register for bank accounts
Last modified: 2018-06-29 22:30:16 UTC
Created attachment 146724 [details] [review] Implements editable transaction date in the register Currently, the only editable date in the register is the bank posting date. This patch implements a second editable date in the first field of the second line of a double-line mode register. The entry date is borrowed in this implementation. I understand the entry date is used for such as stock transactions, but to me is mostly useless for those keeping track of personal finances. This feature has been requested on occasion, such as at https://lists.gnucash.org/pipermail/gnucash-devel/2003-August/010279.html and https://bugzilla.gnome.org/show_bug.cgi?id=92274 and http://lists.gnucash.org/pipermail/gnucash-user/2009-October/031839.html
Comment on attachment 146724 [details] [review] Implements editable transaction date in the register Patch looks good, but can you please elaborate what exactly you mean by "transaction date" as opposed to the current "bank posting date"?
"Transaction date" refers to such as the date the purchase was rung up in the store cash register, payment mailed or possibly received by the recipient, payment received by you, date you walked into the bank to make a deposit, or even the date the expense was scheduled. Your intent to expend the money is definitely determined. "Bank posting date" is when the bank has finally debited or credited your account. "Date entered" in Gnucash would be identical to "transaction date", if you always without fail entered the transaction into Gnucash on the same date as the purchase, bank deposit, etc. Bug 92274 describes it better. That mentions 3 dates, date mailed, date gas company posts the payment, and date the bank debits the payment. I track even more dates on credit card transactions: statement date, date bill received, payment mailing date, card payment received (card transaction) date, card posting date, and bank posting date. These are currently entered into my transaction Notes field, which is one reason for my multi-line up/down Notes field scroll patch, but Notes dates are not sortable. Obviously, the use of sortable dates is flexible. I use one date as a budget date (group budgeted expenses with paychecks), and the second as bank posting date. I could obviously use a third date, the "transaction date", but haven't implemented that yet (much more work).
Comment on attachment 146724 [details] [review] Implements editable transaction date in the register r18428, thanks a lot!
(In reply to comment #0) > Created an attachment (id=146724) [details] [review] > Implements editable transaction date in the register > > Currently, the only editable date in the register is the bank posting date. > This patch implements a second editable date in the first field of the second > line of a double-line mode register. The entry date is borrowed in this > implementation. I understand the entry date is used for such as stock > transactions, but to me is mostly useless for those keeping track of personal > finances. > > This feature has been requested on occasion, such as at > https://lists.gnucash.org/pipermail/gnucash-devel/2003-August/010279.html and > https://bugzilla.gnome.org/show_bug.cgi?id=92274 and > http://lists.gnucash.org/pipermail/gnucash-user/2009-October/031839.html James, While I do understand that having the second date field both visible and editable, this patch has produced a confusing and cluttered register when displaying double line register mode. I am all for choice - but this change should only be introduced if it also includes an option to switch it off. The default register behavior should NOT have this second date field displayed. I would like to see this patch removed until it includes the option functionality described above. Regards, Kim Wood
Based on the feedback received on the mailing list, I have decided to revert the patch for now. (see threads starting at https://lists.gnucash.org/pipermail/gnucash-devel/2010-February/027412.html and https://lists.gnucash.org/pipermail/gnucash-user/2010-February/033612.html ) The primary objections are: * the new field is visually confusing in double line register view * the new field can't be hidden, ie there's no option to not have it * the transaction date is a GnuCash internal field, which should not be user editable. This may be important for example for US tax rules. Suggested improvements, taken from the threads above: * add an option to show or hide the extra field. This gives the users the choice whether or not they want an additional date field. The default for this option should be to hide the new field * don't use the transaction date. Define a new field instead.
Review of attachment 146724 [details] [review]: See previous comment
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=600374. Please continue processing the bug there and please update any external references or bookmarks.