Question on CommandByMail error

RT Users
1

To List,

I’m using CommandByMail and I keep getting this error message, yet the data
is updated:

Failed command 'due: 2010-11-28’
Error message: (no message)

Due: 2010-11-28

The Duse was modified, so why the error message?

I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due:
11-26-2010, etc.

Anyone know why?

Kenn
LBNL

2

I don’t have anything useful to contribute for an answer, other than “Me
too”. I have this exact same issue and I tried every format I could think
of, nothing worked. Eventually I just gave up.

If you figure it out, do let us know (please!)
-JonOn Tue, Nov 9, 2010 at 10:25, Kenneth Crocker kfcrocker@lbl.gov wrote:

To List,

I’m using CommandByMail and I keep getting this error message, yet the data
is updated:

Failed command ‘due: 2010-11-28’
Error message: (no message)

Due: 2010-11-28

The Duse was modified, so why the error message?

I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due:
11-26-2010, etc.

Anyone know why?

Kenn
LBNL

3

Jon,

Actually, I have noticed a couple problems, especially for any Custom Fields
defined as “Text” or “Wiki Text”. Whether I use Gmail, Thunderbird, etc. it
only manages to capture the first 76 characters. I think it needs to be
re-worked for those type of CF’s to capture all text until it runs into
another Field command or “END” or something.

Kenn
LBNLOn Tue, Nov 9, 2010 at 11:15 AM, Jon Davis maillist@konsoletek.com wrote:

I don’t have anything useful to contribute for an answer, other than “Me
too”. I have this exact same issue and I tried every format I could think
of, nothing worked. Eventually I just gave up.

If you figure it out, do let us know (please!)
-Jon

On Tue, Nov 9, 2010 at 10:25, Kenneth Crocker kfcrocker@lbl.gov wrote:

To List,

I’m using CommandByMail and I keep getting this error message, yet the
data is updated:

Failed command ‘due: 2010-11-28’
Error message: (no message)

Due: 2010-11-28

The Duse was modified, so why the error message?

I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due:
11-26-2010, etc.

Anyone know why?

Kenn
LBNL

4

To List,

I’m using CommandByMail and I keep getting this error message, yet the data is updated:

Failed command ‘due: 2010-11-28’
Error message: (no message)

Due: 2010-11-28

The Duse was modified, so why the error message?

I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due: 11-26-2010, etc.

The test suite passes using a timestamp (which is what the
documentation indicates). Does that work for you?

-kevin

5

Kevin,

I don’t understand ‘test suite’ nor what ‘timestamp’ refers to.

KennOn Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone falcone@bestpractical.comwrote:

On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:

To List,

I’m using CommandByMail and I keep getting this error message, yet the
data is updated:

Failed command ‘due: 2010-11-28’
Error message: (no message)

Due: 2010-11-28

The Duse was modified, so why the error message?

I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due:
11-26-2010, etc.

The test suite passes using a timestamp (which is what the
documentation indicates). Does that work for you?

-kevin

6

I don’t understand ‘test suite’ nor what ‘timestamp’ refers to.

The module has a series of tests that are run before a release, and it
passes. That test suite tests Due.

A timestamp is a timestamp, what RT displays dates as by default.

Once you figure it out, documentation patches to make it clearer for
you are welcome in the rt.cpan queue for the module.

-kevin> On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1]falcone@bestpractical.com> wrote:

 On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > To List,
 >
 > I'm using CommandByMail and I keep getting this error message, yet the data is updated:
 >
 > Failed command 'due: 2010-11-28'
 > Error message: (no message)
 >
 > Due: 2010-11-28
 >
 > The Duse was modified, so why the error message?
 >
 > I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due: 11-26-2010, etc.

 The test suite passes using a timestamp (which is what the
 documentation indicates). Does that work for you?
 -kevin

References

Visible links

  1. mailto:falcone@bestpractical.com
7

Kevin,

We ran some transactions with “debug” and this is what we got:

Ok so here is the debug of the process:

[Thu Nov 11 21:38:58 2010] [debug]: Converting ‘ISO-8859-1’ to ‘utf-8’ for
text/plain - Subjectless message (/opt/rt3/bin/…/lib/RT/I18N.pm:231)
[Thu Nov 11 21:38:58 2010] [debug]: Converting ‘ISO-8859-1’ to ‘utf-8’ for
text/html - Subjectless message (/opt/rt3/bin/…/lib/RT/I18N.pm:231)
[Thu Nov 11 21:38:58 2010] [debug]: Guessed encoding: ascii
(/opt/rt3/bin/…/lib/RT/I18N.pm:416)
[Thu Nov 11 21:38:58 2010] [debug]: Guessed encoding: ascii
(/opt/rt3/bin/…/lib/RT/I18N.pm:416)
[Thu Nov 11 21:38:58 2010] [debug]: Found a ticket ID. It’s 85261
(/opt/rt3/bin/…/lib/RT/Interface/Email.pm:1153)
[Thu Nov 11 21:38:58 2010] [debug]: Mail from user #146 (kfcrocker@lbl.gov)
(/opt/rt3/bin/…/lib/RT/Interface/Email/Auth/MailFrom.pm:75)
[Thu Nov 11 21:38:58 2010] [debug]: Running CommandByMail as KFCrocker
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:184)
[Thu Nov 11 21:38:58 2010] [debug]: Found pseudoheader: Priority => 4
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:206)
[Thu Nov 11 21:38:58 2010] [debug]: Found pseudoheader: Due => 2010-11-28
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:206)
[Thu Nov 11 21:38:58 2010] [debug]: Found pseudoheader: Status => new
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:206)
[Thu Nov 11 21:38:58 2010] [debug]: Got command priority => 4
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:213)
[Thu Nov 11 21:38:58 2010] [debug]: Got command due => 2010-11-28
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:213)
[Thu Nov 11 21:38:58 2010] [debug]: Got command status => new
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:213)
[Thu Nov 11 21:38:58 2010] [debug]: Updating Ticket 85261 in Queue Test
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:249)
[Thu Nov 11 21:38:58 2010] [debug]: About to think about scrips for
transaction #345045 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:163)
[Thu Nov 11 21:38:58 2010] [debug]: About to prepare scrips for transaction
#345045 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:167)
[Thu Nov 11 21:38:58 2010] [debug]: Found 0 scrips for TransactionCreate
stage with applicable type(s) Set
(/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:370)
[Thu Nov 11 21:38:58 2010] [debug]: About to commit scrips for transaction
#345045 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:187)
[Thu Nov 11 21:38:58 2010] [debug]: RT::Date used Time::ParseDate to make
‘2010-11-28’ 1290931200 (/opt/rt3/bin/…/lib/RT/Date.pm:222)
[Thu Nov 11 21:38:58 2010] [debug]: About to think about scrips for
transaction #345046 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:163)
[Thu Nov 11 21:38:58 2010] [debug]: About to prepare scrips for transaction
#345046 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:167)
[Thu Nov 11 21:38:58 2010] [debug]: Found 0 scrips for TransactionCreate
stage with applicable type(s) Set
(/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:370)
[Thu Nov 11 21:38:58 2010] [debug]: About to commit scrips for transaction
#345046 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:187)
[Thu Nov 11 21:38:58 2010] [debug]: Guessed encoding: ascii
(/opt/rt3/bin/…/lib/RT/I18N.pm:416)
[Thu Nov 11 21:38:58 2010] [debug]: Guessed encoding: ascii
(/opt/rt3/bin/…/lib/RT/I18N.pm:416)
[Thu Nov 11 21:38:58 2010] [debug]: About to think about scrips for
transaction #345047 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:163)
[Thu Nov 11 21:38:58 2010] [debug]: About to prepare scrips for transaction
#345047 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:167)
[Thu Nov 11 21:38:58 2010] [debug]: Found 0 scrips for TransactionCreate
stage with applicable type(s) Correspond
(/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:370)
[Thu Nov 11 21:38:58 2010] [debug]: About to commit scrips for transaction
#345047 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:187)
[Thu Nov 11 21:38:58 2010] [debug]: About to think about scrips for
transaction #345048 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:163)
[Thu Nov 11 21:38:58 2010] [debug]: About to prepare scrips for transaction
#345048 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:167)
[Thu Nov 11 21:38:58 2010] [debug]: Found 0 scrips for TransactionCreate
stage with applicable type(s) Status
(/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:370)
[Thu Nov 11 21:38:58 2010] [debug]: About to commit scrips for transaction
#345048 (/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:187)
[Thu Nov 11 21:38:58 2010] [warning]: Failed command ‘due: 2010-11-28’
Error message: (no message)
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:696)
[Thu Nov 11 21:38:58 2010] [crit]: Failed command ‘due: 2010-11-28’
Error message: (no message) (/opt/rt3/bin/…/lib/RT/Interface/Email.pm:244)
[Thu Nov 11 21:38:58 2010] [debug]: Found 16 scrips for TransactionBatch
stage with applicable type(s) Set,Correspond,Status
(/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:370)
[Thu Nov 11 21:38:59 2010] [debug]: Loaded $cf_obj->Name = Description
((eval 471):37)
[Thu Nov 11 21:38:59 2010] [error]: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1046)
[Thu Nov 11 21:38:59 2010] [error]: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1046)
[Thu Nov 11 21:38:59 2010] [error]: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1046)
[Thu Nov 11 21:38:59 2010] [error]: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt3/bin/…/lib/RT/Group_Overlay.pm:1046)
[Thu Nov 11 21:38:59 2010] [debug]: Committing scrip #52237 on txn #345045
of ticket #85261 (/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:190)

What seems odd is that the ticket is updated, but we get the error message.

My question is, can you think of how this might have happened or point me in
a direction to look?

Thanks.

Kenn
LBNLOn Tue, Nov 9, 2010 at 1:27 PM, Kevin Falcone falcone@bestpractical.comwrote:

On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote:

I don’t understand ‘test suite’ nor what ‘timestamp’ refers to.

The module has a series of tests that are run before a release, and it
passes. That test suite tests Due.

A timestamp is a timestamp, what RT displays dates as by default.

Once you figure it out, documentation patches to make it clearer for
you are welcome in the rt.cpan queue for the module.

-kevin

On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1] falcone@bestpractical.com> wrote:

 On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > To List,
 >
 > I'm using CommandByMail and I keep getting this error message, yet

the data is updated:

 >
 > Failed command 'due: 2010-11-28'
 > Error message: (no message)
 >
 > Due: 2010-11-28
 >
 > The Duse was modified, so why the error message?
 >
 > I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28;

Due: 11-26-2010, etc.

 The test suite passes using a timestamp (which is what the
 documentation indicates). Does that work for you?
 -kevin

References

Visible links

  1. mailto:falcone@bestpractical.com
8

[Thu Nov 11 21:38:58 2010] [warning]: Failed command ‘due: 2010-11-28’

My question is, can you think of how this might have happened or point me in a direction to
look?

This is not a Timestamp, it is a Date. A Timestamp includes a Time.

There are examples in the test suite that ships as part of the
extension. Patches to update the README would be great.

-kevin> On Tue, Nov 9, 2010 at 1:27 PM, Kevin Falcone <[2]falcone@bestpractical.com> wrote:

 On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote:
 > I don't understand 'test suite' nor what 'timestamp' refers to.

 The module has a series of tests that are run before a release, and it
 passes. That test suite tests Due.

 A timestamp is a timestamp, what RT displays dates as by default.

 Once you figure it out, documentation patches to make it clearer for
 you are welcome in the rt.cpan queue for the module.

 -kevin
 > On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1][3]falcone@bestpractical.com> wrote:
 >
 > On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > > To List,
 > >
 > > I'm using CommandByMail and I keep getting this error message, yet the data is updated:
 > >
 > > Failed command 'due: 2010-11-28'
 > > Error message: (no message)
 > >
 > > Due: 2010-11-28
 > >
 > > The Duse was modified, so why the error message?
 > >
 > > I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due: 11-26-2010, etc.
 >
 > The test suite passes using a timestamp (which is what the
 > documentation indicates). Does that work for you?
 > -kevin
9

Kevin,

Actually, I wasn’t concerned with a timestamp. I’m more concerned with why
I’m getting an error message even though the ticket fields are updated using
CommandByMail. That’s why I included the “debug” info in my last note.
Do you have any ideas on where I can look for the problem?

Kenn
LBNLOn Thu, Nov 11, 2010 at 4:12 PM, Kevin Falcone falcone@bestpractical.comwrote:

On Thu, Nov 11, 2010 at 01:53:39PM -0800, Kenneth Crocker wrote:

[Thu Nov 11 21:38:58 2010] [warning]: Failed command ‘due: 2010-11-28’

My question is, can you think of how this might have happened or point
me in a direction to
look?

This is not a Timestamp, it is a Date. A Timestamp includes a Time.

There are examples in the test suite that ships as part of the
extension. Patches to update the README would be great.

-kevin

On Tue, Nov 9, 2010 at 1:27 PM, Kevin Falcone <[2] falcone@bestpractical.com> wrote:

 On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote:
 > I don't understand 'test suite' nor what 'timestamp' refers to.

 The module has a series of tests that are run before a release, and

it

 passes. That test suite tests Due.

 A timestamp is a timestamp, what RT displays dates as by default.

 Once you figure it out, documentation patches to make it clearer for
 you are welcome in the rt.cpan queue for the module.

 -kevin
 > On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1][3] falcone@bestpractical.com> wrote:
 >
 > On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > > To List,
 > >
 > > I'm using CommandByMail and I keep getting this error message,

yet the data is updated:

 > >
 > > Failed command 'due: 2010-11-28'
 > > Error message: (no message)
 > >
 > > Due: 2010-11-28
 > >
 > > The Duse was modified, so why the error message?
 > >
 > > I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28;

Due: 11-26-2010, etc.

 >
 > The test suite passes using a timestamp (which is what the
 > documentation indicates). Does that work for you?
 > -kevin
10

Actually, I wasn’t concerned with a timestamp. I’m more concerned with why I’m getting an
error message even though the ticket fields are updated using CommandByMail. That’s why I
included the “debug” info in my last note.
Do you have any ideas on where I can look for the problem?

Because the Due fails (according to your logs). So it logs an error.
Perhaps you could be clearer about “the ticket fields are updated”
since you started this thread saying that Due doesn’t work and then
showed logs where Due doesn’t work because you’re using the wrong
format.

-kevin> On Thu, Nov 11, 2010 at 4:12 PM, Kevin Falcone <[1]falcone@bestpractical.com> wrote:

 On Thu, Nov 11, 2010 at 01:53:39PM -0800, Kenneth Crocker wrote:
 > [Thu Nov 11 21:38:58 2010] [warning]: Failed command 'due: 2010-11-28'
 >
 > My question is, can you think of how this might have happened or point me in a direction
 to
 > look?

 This is not a Timestamp, it is a Date. A Timestamp includes a Time.

 There are examples in the test suite that ships as part of the
 extension. Patches to update the README would be great.
 -kevin
 > On Tue, Nov 9, 2010 at 1:27 PM, Kevin Falcone <[2][2]falcone@bestpractical.com> wrote:
 >
 > On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote:
 > > I don't understand 'test suite' nor what 'timestamp' refers to.
 >
 > The module has a series of tests that are run before a release, and it
 > passes. That test suite tests Due.
 >
 > A timestamp is a timestamp, what RT displays dates as by default.
 >
 > Once you figure it out, documentation patches to make it clearer for
 > you are welcome in the rt.cpan queue for the module.
 >
 > -kevin
 > > On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1][3][3]falcone@bestpractical.com> wrote:
 > >
 > > On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > > > To List,
 > > >
 > > > I'm using CommandByMail and I keep getting this error message, yet the data is
 updated:
 > > >
 > > > Failed command 'due: 2010-11-28'
 > > > Error message: (no message)
 > > >
 > > > Due: 2010-11-28
 > > >
 > > > The Duse was modified, so why the error message?
 > > >
 > > > I tried this several times, ie. Due:11-26-2010; Due: 2010-11-28; Due: 11-26-2010, etc.
 > >
 > > The test suite passes using a timestamp (which is what the
 > > documentation indicates). Does that work for you?
 > > -kevin

References

Visible links

  1. mailto:falcone@bestpractical.com
  2. mailto:falcone@bestpractical.com
  3. mailto:falcone@bestpractical.com
11

Kevin,

My apologies. I thought I had been clear. I’m not seeing where the format is
wrong. I looked at the Tools->Offline template and used that as a basis for
my template.
Due:followed by a date

Are you saying the format I use for the date itself is wrong?

Kenn
LBNLOn Fri, Nov 12, 2010 at 9:17 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Fri, Nov 12, 2010 at 09:11:43AM -0800, Kenneth Crocker wrote:

Actually, I wasn’t concerned with a timestamp. I’m more concerned with
why I’m getting an
error message even though the ticket fields are updated using
CommandByMail. That’s why I
included the “debug” info in my last note.
Do you have any ideas on where I can look for the problem?

Because the Due fails (according to your logs). So it logs an error.
Perhaps you could be clearer about “the ticket fields are updated”
since you started this thread saying that Due doesn’t work and then
showed logs where Due doesn’t work because you’re using the wrong
format.

-kevin

On Thu, Nov 11, 2010 at 4:12 PM, Kevin Falcone <[1] falcone@bestpractical.com> wrote:

 On Thu, Nov 11, 2010 at 01:53:39PM -0800, Kenneth Crocker wrote:
 > [Thu Nov 11 21:38:58 2010] [warning]: Failed command 'due:

2010-11-28’

 >
 > My question is, can you think of how this might have happened or

point me in a direction

 to
 > look?

 This is not a Timestamp, it is a Date. A Timestamp includes a Time.

 There are examples in the test suite that ships as part of the
 extension. Patches to update the README would be great.
 -kevin
 > On Tue, Nov 9, 2010 at 1:27 PM, Kevin Falcone <[2][2] falcone@bestpractical.com> wrote:
 >
 > On Tue, Nov 09, 2010 at 01:22:51PM -0800, Kenneth Crocker wrote:
 > > I don't understand 'test suite' nor what 'timestamp' refers to.
 >
 > The module has a series of tests that are run before a release,

and it

 > passes. That test suite tests Due.
 >
 > A timestamp is a timestamp, what RT displays dates as by default.
 >
 > Once you figure it out, documentation patches to make it clearer

for

 > you are welcome in the rt.cpan queue for the module.
 >
 > -kevin
 > > On Tue, Nov 9, 2010 at 12:52 PM, Kevin Falcone <[1][3][3] falcone@bestpractical.com> wrote:
 > >
 > > On Tue, Nov 09, 2010 at 10:25:57AM -0800, Kenneth Crocker wrote:
 > > > To List,
 > > >
 > > > I'm using CommandByMail and I keep getting this error message,

yet the data is

 updated:
 > > >
 > > > Failed command 'due: 2010-11-28'
 > > > Error message: (no message)
 > > >
 > > > Due: 2010-11-28
 > > >
 > > > The Duse was modified, so why the error message?
 > > >
 > > > I tried this several times, ie. Due:11-26-2010; Due:

2010-11-28; Due: 11-26-2010, etc.

 > >
 > > The test suite passes using a timestamp (which is what the
 > > documentation indicates). Does that work for you?
 > > -kevin

References

Visible links

  1. mailto:falcone@bestpractical.com
  2. mailto:falcone@bestpractical.com
  3. mailto:falcone@bestpractical.com
12

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]falcone@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]falcone@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
13

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
LBNLOn Fri, Nov 12, 2010 at 9:32 AM, Kevin Falcone falcone@bestpractical.comwrote:

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] falcone@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]

falcone@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
14

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.

That is irrelevant.
The module does not pay attention to your date settings.

It takes a Timestamp

-kevin

15

Hello,

I encounter the same problem, and tried to identify what the difference is between timestamp and what I entered in the field “Due:”.

My mail is only (except object of the email referring to an existing ticket) :

Due:2011-05-09 16:00:00

And I receive :
Failed command ‘due: 2011-05-09 16:00:00’
Error message: (no message)

And effectively, the field is correctly updated in the ticket.
Can someone point me how to generate a “good” timestamp ?

Cdt,

Franck CALLEJA-ALBILLOS
TREFLE pour Alcatel-Lucent
Centre de Compétences Managed Services - IP/MPLS

Tél. : +33 1 30 77 1362
Email : franck.calleja-albillos@alcatel-lucent.com

-----Message d’origine-----De : rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] De la part de Kevin Falcone
Envoyé : vendredi 12 novembre 2010 20:23
À : rt-users@lists.bestpractical.com
Objet : Re: [rt-users] Question on CommandByMail error

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.

That is irrelevant.
The module does not pay attention to your date settings.

It takes a Timestamp

-kevin