Looks great Graham. I noticed you are using approximatedate for the 'Last checked' column, which I think is correct, as seeing 3 days ago would be more helpful to me than 2010-04-06, but it seems that approximatedate only does so if the timedelta is <= 1 day... do you know why this is?
Also why not simply use 'Last check' as the column heading? (ie. a noun, like 'Next check' and the other column headers).
Very insignificant thought regarding the ordering of the 2 col dls, would it be easier to scan if Created/Changed and Checked/Scheduled where vertically aligned like this:
Tracker | Remote bug id
Last status | Created
Checked | Changed
Scheduled | Created by
Looks great Graham. I noticed you are using approximatedate for the 'Last checked' column, which I think is correct, as seeing 3 days ago would be more helpful to me than 2010-04-06, but it seems that approximatedate only does so if the timedelta is <= 1 day... do you know why this is?
Also why not simply use 'Last check' as the column heading? (ie. a noun, like 'Next check' and the other column headers).
Very insignificant thought regarding the ordering of the 2 col dls, would it be easier to scan if Created/Changed and Checked/Scheduled where vertically aligned like this:
Tracker | Remote bug id
Last status | Created
Checked | Changed
Scheduled | Created by
Anyway, approved either way.