ThinkingRock Forum

Just a few 'quirks'...

Q1:
In the actions list, the sorting seems to be a bit strange. If I sort on a date column, the actions are sorted correctly, but the actions with a date set are placed below the ones without an entry in that field. That is, the DoASAP entries are listed before the ones with a date set. I would prefer to have the scheduled entries (presumably the ones that are most important to keep in plain view) at the top and the DoASAPs below. Is there a way to fix this?

Q2:
Is the default sorting of the list the same as when clicking on the header of the 'done tickbox' column? If not: How do I restore the default sorting after clicking on a column header?

Q3:
I understand that some sorting options will be available in the final release. Will that include sorting on dates regardless of which date is set? Due date and action date (and maybe start date) would be the likely useful candidates here.

To clarify what I mean, say you have two entries with action dates 10. and 12. and one entry with due date 11. The sort sequence would be first action date, due date, second action date. (Q1 is relevant here too.)

Reasoning: Due date and action date have a very similar meaning, but are used for different kind of entries. Scheduled and deferred actions use action date, projects and DoASAPs use due date. Sometimes it would be natural to have them intermixed.

...in my mind at least.

Frode

Just thinking a bit further...
Would it be possible to have a single date field covering both uses? If I've got it right, the two fields are never used simultaneously for an action/project. If so, it would be a matter of finding a common name for these two uses that would sound natural. (Apart from the change in code that I don't know the extent of.)

Maybe the change would only entail having an extra virtual report column or criteria for sorting/filtering in the reports.

I don't want to jump the gun here, but if this sounds like somthing to implement, would it be in 2.0 or later? I suppose there must be a feature freeze at some time?

Regards, Frode

Err... me too.

This is issue 3 that I've come across while trying to learn TR. I think Frode has hit in on the head with his thinking of sorting via the dates... at least I think exactly the same way he does!

I think the biggest issue in what he notes is the sorting of date fields; to me/us it's sort of backwards. While I was trying to nut how to use it (I figured maybe I was just doing something wrong), it occurred to me that the problem could be fixed by not treating empty date fields as automatically lower than every other date. e.g. in the sorting, if an action doesn't have a date set, assume it has a date of like Jan 1, 9999 and therefore they will always drop to the *bottom* of the list instead of the top like they do now when doing an ascending date sort.

I think that these are good suggestions. Especially the non-precedence of the empty date fields.

Good to know that it's not just me..



If I could use this instead of the 'due date' and 'action date' columns, it would really help with my cramped laptop screen. Sometimes it's difficult to get column widths that are good to view quickly.

Frode

PS
Should this thread be moved to the 'Suggestions' list?