Suggestion: "Creation date" > split date & time

[G-Eric]

Hi Dan,

Fact: the field "Creation date" contains both date and time of record creation.

• Other date/time related fields (e.g. start, due, completed) have date and time attributes splitted, with a label according to the contents (i.e. "start date" for the date + "start time" for the time).
• When you used the field labelled "creation date" with intention to sort records by creation date (only, i.e. no time impact), you can't efficiently have a 2nd level key to sort the records  >>  the creation time (included in the field) forces implicitely a 2nd sorting level, cancelling any other criteria impact.
  Usage:
  - e.g. a view day by day of who did create what (as incoming requests overview)
  - e.g. a list day by day of created tasks "by title" (as team meeting agenda)
  

For these reasons, I would suggest to split existing "Creation date" (with date+time) in "Creation date" (date) and "Creation time" (time).

Now, I know this is theory as a (direct) main issue to implement this (if found relevant and acceptable, of course) might be the technical impact (how to split records in existing db, retro compatibility, rewrite of program where merged criteria used today, ...).
But it sounds to me to make sense at least to think about it for the future for a consistency approach of field labels and contents usage.

Thanks & Merry Xmas - Eric

[.dan.g.]

Hi Eric

It looks like I already modified 7.1 to only display the creation date (presumably because I also saw that the creation time is largely irrelevant), though there is a bug where it is still currently showing a default time.

So hopefully that will solve your problem when it is fixed.

Merry Xmas.

Dan

[G-Eric]

'Creation Date' field format adjustement implemented in v7.11 (i.e. now contains only 'date' component) - Thanks Dan