Bug 37193
Summary: | Previous balances go bad when entering new xaction. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Powertools | Reporter: | Kirk Morrow <kirk_morrow> | ||||||
Component: | gnucash | Assignee: | Tim Powers <timp> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 7.1 | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2001-04-24 17:41:58 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Kirk Morrow
2001-04-23 13:10:20 UTC
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 reproduce this. Tim 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 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=37193 I will contact them as well. Until there's a fix, use the mouse as a workaround :/ Tim 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 expected behaviour. Tim 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. |