Incorrect/confusing ordering of transactions
-
Virgil Dupras
- State changed from new to accepted
- Tag set to bug
I can reproduce the error with these steps:
- Open the moneyguru file attached to the ticket.
- Open the "a/c" account.
- Click on the "Date" column to invert the sort order.
- 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
- Assigned user set to Virgil Dupras
-
Virgil Dupras
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
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
- State changed from accepted to fixed
(from [97dab691a584]) [#328 Incorrect/confusing ordering of transactions 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.

