Sort transactions new to old

David T. sunfish62 at yahoo.com
Thu Oct 18 14:52:21 EDT 2012


Fred--

If I had to guess at the OP's problem, I would hazard that he had imported a bunch of transactions, and was editing them to be human friendly, or to change accounts. Thus, he would be "working through" transactions that were already there.

I have found Gnucash's register behavior to be something I had to either work around or get used to in this regard; I import a lot of transactions, and when I edit the transactions, I find the seemingly spontaneous (I do know that it is based on measurable interface principles) reordering of transactions a challenge. 

This goes beyond the jarring jump that happens when you change the date of an existing transaction (as when you might move a check from its date of cashing to its date of writing); I have found that if you have a bunch of transactions for a given date, and edit them for any reason, the transaction order within the day is inverted. Thus, if you start with the "first" transaction in the date, editing it moves it to the other end of the date. My ugly workaround is to leave my mouse pointer at the same literal spot on my screen, and as I edit each transaction on the day, I carefully click the mouse pointer in the same spot, which opens a new transaction because Gnucash rearranges the transactions.


David



________________________________
 From: Fred Bone <Fred.Bone at dial.pipex.com>
To: Chris Lonsberry <chris.lonsberry at gmail.com> 
Cc: gnucash-user at gnucash.org 
Sent: Thursday, October 18, 2012 10:46 AM
Subject: Re: Sort transactions new to old
 
On 18 October 2012 at 4:35, Chris Lonsberry said:

> Hi all,
> 
> Just getting started with GnuCash (after becoming way too annoyed with
> Mint to continue using it). Very happy so far!
> 
> I've discovered that the ability to sort new to old rather than old to new
> does not currently exist. Is there a way to post a feature request for
> GnuCash? I would imagine reverse sorting would be a fairly simple feature
> to implement.
> 
> Why? If I have a lot of transactions to work through, I prefer to start
> with the new ones rather than the old ones, but when working from new to
> old the cursor always goes to the next, blank transaction after I finish
> with each transaction. That requires me to manually select the previous
> transaction. It adds up to a lot of extra clicking or tabbing when you
> want to work reverse chronological.

I for one don't understand why you need to "manually select" a "previous 
transaction" when entering a batch of transactions. Why not complete each 
one before moving on to the next?

_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


More information about the gnucash-user mailing list