#328 Incorrect/confusing ordering of transactions - moneyGuru

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#328 ✓fixed

Incorrect/confusing ordering of transactions

Reported by Rhys Parry | June 11th, 2012 @ 11:46 PM

Please see the attached files. This is a distilled down version of something I saw on a larger data set.

The balance is show at £1000 on 1st July.
A scheduled transaction for -£20 is shown next, but the balance is somehow £880. I would expect £980 here.
The next line is a regular transaction for £100. The balance is shown as £900. I would expect £880.
The next is a scheduled transaction for -£20 again. It the balance looks like it has recovered correctly here.

It looks like transactions 2 & 3 were processed in the opposite order to that shown. In my original case there were many more transactions, so it was harder to work out what was going on.

dodgyaddition.png 94.3 KB
july12_dodgy.moneyguru 881 Bytes

Comments and changes to this ticket

Virgil Dupras June 12th, 2012 @ 04:33 PM
- State changed from “new” to “accepted”
- Tag set to “bug”
I can reproduce the error with these steps:
1. Open the moneyguru file attached to the ticket.
2. Open the "a/c" account.
3. Click on the "Date" column to invert the sort order.
4. Click on the "Date" column again to bring it back.
The result is that the schedule spawn, which was supposed to be after the regular transaction is now before it.
Virgil Dupras June 18th, 2012 @ 06:20 PM
- Assigned user set to “Virgil Dupras”
Virgil Dupras June 18th, 2012 @ 06:44 PM
As I was trying to create an automated test for this, an important detail emerged: For this bug to happen, the document has to be saved and reloaded.
Virgil Dupras June 18th, 2012 @ 06:55 PM
Oh, it has nothing to do with save/reload after all, it's just that reloaded transactions have a +1 on their "position" attribute. We can reproduce the problem without reloading if we have 2 transactions and a spawn on the same date.
Virgil Dupras June 18th, 2012 @ 07:05 PM
- State changed from “accepted” to “fixed”
(from [97dab691a584]) [#328 state:fixed] Fixed sorting inconsistency in transaction tables when schedule spawns were involved. https://bitbucket.org/hsoft/moneyguru/changeset/97dab691a584/

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.