Changes between Version 13 and Version 14 of Email2tracParse


Ignore:
Timestamp:
02/06/12 13:25:31 (11 years ago)
Author:
bas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Email2tracParse

    v13 v14  
    1616 1. discussion, Only if the [http://trac-hacks.org/wiki/DiscussionPlugin DiscussionPlugin] is installed. If not then a ticket will be created.
    1717
     18==== tickets ====
    1819How is the 'Subject' line parsed for tickets:
    1920 * Subject: Bas
     
    2526 * Subject: !#4?owner=jaap: Bas
    2627  * will update ticket !#4 and set owner to jaap
     28
     29==== blog ====
    2730 * Subject: blog:bas
    28   * Will create a blog entry ''only'' if the  [http://trac-hacks.org/wiki/FullBlogPlugin FullBlogPlugin] is installed
    29  * Subject: blog:3 bas
    30   * Will update a blog entry
     31  * Will create a blog entry, with its short name derived from the
     32   email's date, and title 'Bas'. ''only'' if the  [http://trac-hacks.org/wiki/FullBlogPlugin FullBlogPlugin] is installed
     33
     34 * `Subject: blog?categories=foo,bar&author=joe: Bas`
     35  * Will create a new blog entry and set categories to 'foo' and 'bar',and author to 'joe'. Categories can be separated by comma, semicolon or space, and they cannot contain ampersand or colon.
     36
     37 * `Subject: blog:test Bas`
     38  * Will create a new blog entry with name 'test' ''or'' add a comment to that blog entry if it already exists.  Note that the subject of the email is not preserved when a comment is added to a blog entry.
     39
     40
    3141
    3242== Body ==
     
    8595}}}
    8696
    87 === Update ticket fields ===
     97== Inline properties ==
    8898
    89 If the ''inline_properties'' is set in ''email2trac.conf'' then we can update ticket fields within the body text, eg:
     99
     100If the ''inline_properties'' is set in ''email2trac.conf'' then we can update
     101ticket or blog fields within the body text.
     102
     103=== ticket ===
     104
     105To update ticket field within the body text: eg:
    90106{{{
    91107This is a Test1234
     
    105121@<ticket field name> : <value>
    106122}}}
     123
     124=== blog ===
     125
     126If `inline_properties` are enabled, `@categories` , `@author` and
     127`@update` can be used in the mail body. Inline properties take
     128precedence over parameters given in the 'Subject:' header.