Changes between Version 138 and Version 139 of Email2tracConfiguration


Ignore:
Timestamp:
10/03/13 09:48:04 (11 years ago)
Author:
bas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Email2tracConfiguration

    v138 v139  
    124124
    125125== Ticket Update ==
    126 If you have enabled ''ticket_update'' in  [wiki:Email2tracConfiguration email2trac.conf] then you have to configure  one of the two options explained below.  Email2trac will scan the subject field of all emails to determine if a given email is a ticket update, and consequently it must update ticket fields.
    127 
    128 For example:
    129 
    130  * This subject line will trigger an update of ticket number 1529:
    131 {{{
    132 Subject: [hic] #1529: Re: LRZ
    133 }}}
    134 
    135  * The following subject line will trigger an update of ticket number 1529 and will set its owner to ''bas'' and priority to ''medium'':
    136 {{{
    137 Subject: [hic] #1529?owner=bas&priority=medium: Re: LRZ
    138 }}}
    139 
    140 ''NOTE:  For versions prior to 1.1.0 the subject field separator is , instead of &''
    141 
    142 === Email address ===
     126
     127If you have enabled ''ticket_update''in  [wiki:Email2tracConfiguration email2trac.conf] then it will parse the subject line to determine if this a reply
     128mail. Optional you can set ''ticket_update_by_subject'' option to see if we have matching subject line.  See [wiki:Email2tracParse How an email message is parsed]
     129
     130At SURFsara we use the setup that is described below.
     131
     132=== Ticket Email address ===
    143133This is the preferred method. This will setup an email address  where the ticket information will be sent to. This is a different  email address than the ticket email address.  When you reply on  this email a copy will be sent to the ticket email address.
    144134