[rt-users] Revisiting CommandByMail problem

Kevin Falcone falcone at bestpractical.com
Mon Nov 22 19:53:27 EST 2010


On Mon, Nov 22, 2010 at 02:01:00PM -0800, Kenneth Crocker wrote:
>    To List,
> 
>    I've continued to have problems with getting an error message from RT when using CommandByMail
>    and I found an interesting situation:
> 
>    When I create a ticket using email and include many fields (dates and otherwise), the ticket
>    is created and I get no error message back.
> 
>    When I try to update a ticket using CommandByMail (referencing the ticket in the Subject
>    line), the ticket is updated, yet I get an error message back from RT in email stating errord
>    for the date fields. Yet the data WAS updated.
> 
>    I went to the rt.log and noticed that the update fields get updated, then a transaction Type
>    "Correspond" is processed and THEN the error messages get sent.
> 
>    I then went to the DataBase and looked at the TRANSACTION Table and found the transactions and
>    sure enough, there is a transaction record Type "Set" for each date field and any other fields
>    all followed by that "Correspond": Type trans record. I also noticed that regardless of what
>    non-date fields I am updating in sequence after the date fields, the transactions for the date
>    fields are always processed last just before the transaction type "correspond".
> 
>    I just did a complete install of CommandByMail to ensure I hadn't accidentally messed up any
>    files.
> 
>    So, I have two questions:
> 
>    1) Why does the "Create" email work without any error messages and the "Update" work but send
>    error messages?
>    2) Why would CBM go ahead and update the ticket and then only when it processes the
>    "Correspond" transaction decide to send out error messages for the date fields?

If you're passing a correctly formatted Due date on Correspond emails
and getting errors, then that may well be a bug.  Your previous emails
have shown that you weren't passing a valid Due date.

The easiest way to get this fixed is a patch that adds a failing test
to the testsuite.

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20101122/7b904bcc/attachment.sig>


More information about the rt-users mailing list