Red Hat Bugzilla – Bug 37193
Previous balances go bad when entering new xaction.
Last modified: 2008-05-01 11:38:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i586)
When entering a new transaction into a register, the balance on the last
few transactions will change to incorrect values. It seems to occurs
mostly with transactions where funds are transfered from one account to
another. In this case, all transactions since the last transfer from the
same other account are affected, regardless if the date of the new
transaction is later than the transactions in between.
Steps to Reproduce:
1. In the register for account "X" record a transaction of funds from
account "Y" and use a unique "Description" for the transaction.
2. Enter a several transactions with dates after the transaction above.
3. Start entering with the same description as that used in Step 1, but
with a date later than all those above.
4. As you tab out of the description field and GnuCash remembers the
previous transaction values from step 1, watch the above balances change.
Actual Results: The final balances on previous transactions change to
Expected Results: The balances should not have been affected and stayed
I can't reproduce the problem. I created two separte accounts, checking and
savings. Tranferred money between the two, did some random transactions, then
used the same description as in step 1 to transfer to the other account. I can't
Created attachment 16125 [details]
GnuCash file showing error
1. Open the file attached above with GnuCash
2. Open the Mortgage Y register
3. Enter "HomeSide Lending" in the Description field.
4. Watch the balance when you Tab to the next field.
This is weird, it *only* happens if you use tab to change feilds (using the
mouse doesn't show the problem).
Can you please report this to the gnucash folks and refer them to
I will contact them as well.
Until there's a fix, use the mouse as a workaround :/
Created attachment 16246 [details]
GnuCash screenshot of bug 37193
I just got mail from one if the authors, I am CC'ing my response back to you. In
short (for the purposes of bugzilla), it seems it is confusing, although
If entering a transaction with a date previous to other transactions, it will
update the register as you tab between fields. So if transactions are entered
with a future date and then a current dated transaction is enter, it will alter
the values. I'm going to go ahead and close this as a bug. I'll though I don't
like this behavior, it's not really a bug. The values are mathematically
correct after all.