After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611768 - Cannot edit Note field of reconciled transaction
Cannot edit Note field of reconciled transaction
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Register
2.3.x
Other Linux
: Normal normal
: ---
Assigned To: David Hampton
Chris Shoemaker
Depends on:
Blocks:
 
 
Reported: 2010-03-04 03:23 UTC by Tommy Trussell
Modified: 2018-06-29 22:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tommy Trussell 2010-03-04 03:23:31 UTC
Once a transaction has been reconciled using Actions --> Reconcile..., you can go back and edit a split memo and account, but you cannot change the transaction Note (the field immediately below the Description field in the Double Line register).

The transaction Description is protected from changes and that seems good and of course the transaction memo, account and amount that are bound to that bank or credit card's register should be protected, but I think you SHOULD be able to edit the Notes field.

For example I may have a transaction that, when I was reconciling the amount I thought I had lost the receipt, so I created a new transaction based on the amount on the statement and put "missing receipt" in the Note field. Later I found the missing receipt, but now I cannot edit the Notes field to reflect the actual content of the item.

I first noticed this behavior in 2.2.9 and I verified it still works the same way in 2.3.10.

Let me know if there is a logical reason to prevent this field from being edited.
Comment 1 Bob 2012-08-18 12:21:29 UTC
This is probably to late and using the trunk version when the transaction is reconciled and you then try to change a field, a pop up dialogue will be displayed that allows you to disable this warning forever or just the current session which will then allow you to update the field.

There is a situation described in bug 610648 that would seem to lock it forever that you may of come across with steps to overcome it.


I think this can be closed.
Comment 2 Mike Evans 2013-10-04 13:42:19 UTC
I think Bug 610648 covers this scenario.  Closing this as obsolete as suggested.
Comment 3 John Ralls 2018-06-29 22:36:03 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=611768. Please update any external references or bookmarks.