Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Incorrect/confusing ordering of transactions

#328

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

  1. The balance is show at £1000 on 1st July.
  2. A scheduled transaction for -£20 is shown next, but the balance is somehow £880. I would expect £980 here.
  3. The next line is a regular transaction for £100. The balance is shown as £900. I would expect £880.
  4. 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.

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

State: fixed
Milestone: none
Assigned to: Virgil Dupras Virgil Dupras

Activity

  1. Virgil Dupras
    Virgil Dupras
    • 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.

    June 12th, 2012 @ 04:33 PM

  2. Virgil Dupras
    Virgil Dupras
    • Assigned user set to Virgil Dupras

    June 18th, 2012 @ 06:20 PM

  3. 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.

    June 18th, 2012 @ 06:44 PM

  4. Virgil Dupras
    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.

    June 18th, 2012 @ 06:55 PM

  5. Virgil Dupras
    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/

    June 18th, 2012 @ 07:05 PM

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.