Something broken about sorting

[sarev]

When using the current timesheet as a template for next week, the old behaviour was to have the rows sorted in the same order as the timesheet being copied. Now, the rows are in some "random" order.

In addition, using the sort facility to reorder them often results in only partially sorted rows the first time around - you have to do it twice to get the desired results. This is clearly a bug.

As a final note, it'd be nice if the "Choose order..." menu defaulted to some pre-defined sorting order (as in, your favourite) because I often forget to set that and just hit "Sort ascending" only to have nothing useful happen before I remember I have to select something from the menu first. Long story short, I want timesheets sorted by customer/project and I'm having to do ever more clicks for each new timesheet (and each time I add a new task to a timesheet) just to achieve that.

See the images below for an example session of creating a new timesheet using the old one as a template and then trying to sort by customer/project...

Initial order - no idea what this is...

After sorting by customer/project - it's got some of the way there...

After sorting by customer/project again - success - until I add a new task :(

[sarev]

"As a final note, it'd be nice if the "Choose order..." menu defaulted to some pre-defined sorting order (as in, your favourite)"

What I actually mean here is that the sort order should be sticky for a timesheet (the sort order is an attribute of a timesheet 'object') - so when you use it as a template, the new one inherits that sort order. If you sort it by some other order, it sticks with that new order. When you add new tasks, it's re-sorted for you.

[pond]

The referencing issues will be used to track the individual components of this report. When all of them are closed, this one will be closed too.

[pond]

(Note to self: Use the "Comment" button instead of the "Close & Comment" button next time).

[pond]

All related issues are now fixed/implemented and thus closed, so closing this one.