Kevin, I'm sorry. I know I'm hard to deal with. We don't use timestamp on any of our dates. We just use dates. Our global system default is time=>0 in our date format: *Set($DateTimeFormat, {Format => 'LocalizedDate', Time => 0,});
*So when we want to set a date, we just want the date, hence "Due: 2010-11-15". However, if you're saying the format of the date itself (2010-11-15) is wrong, then I am wondering what it should be since our "LocalizedDate" format is yyyy-mm-dd. Is that a clearer explanation of where I'm coming from? Kenn LBNL * * On Fri, Nov 12, 2010 at 9:32 AM, Kevin Falcone <falc...@bestpractical.com>wrote: > On Fri, Nov 12, 2010 at 09:27:16AM -0800, Kenneth Crocker wrote: > > Are you saying the format I use for the date itself is wrong? > > Yes. Your format is wrong. > > I believe I've said that in each reply (I've snipped them below) > > -kevin > > > > On Thu, Nov 11, 2010 at 4:12 PM, Kevin Falcone <[1][2] > falc...@bestpractical.com> wrote: > > > This is not a Timestamp, it is a Date. A Timestamp includes a > Time. > > > > > > On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote: > > > > A timestamp is a timestamp, what RT displays dates as by > default. > > > > > > On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1][3][3][4] > falc...@bestpractical.com> > > > > > > I tried this several times, ie. Due:11-26-2010; Due: > 2010-11-28; Due: 11-26-2010, > > > > > The test suite passes using a timestamp (which is what the >