When importing from CSV, dates order is wrong

[AAverin]

Because there is no "time" in CSV imports, only date, when importing, transactions end up in the wrong order.
When importing CSV, it should be possible to say in which order transactions should be put. At the moment, Buckets inverts transactions order and my latest transactions and up at the bottom.

For example, in the CSV transactions will be ordered with latest being on the top of the list
After the import, those transactions end up at the bottom of the list, sorted by date

[iffy]

@AAverin From your description, it would be sufficient to add an option to import in reverse order, right?

[AAverin]

@iffy depends on how the import actually works.
I assume it's in reverse order, but if you order by date, and all date entires are equal – resulting order will depend on the sorting algorithm you use =) They can be just mixed

I would propose to add +1 second to every entry in CSV starting from the bottom, and then sort by date+time. Then you can apply the order and support reverse, if necessary, but all entries will have stable place in transactions

[iffy]

@AAverin I guess I'm asking if the CSV has them in the correct order (or the correct reverse order). If it does, then adding the sort option ought to work (using the incrementing internal transaction id as the tie-breaker for transactions on the same date).

[AAverin]

CSVs that I used so far were in the correct order, but exposed only the date of the transaction and not the time.

[iffy]

Included in v0.65.0 release (AUTOMATED COMMENT)