Subject

This field processor uses content in the format #key="some long value".  The key is prefixed with the # symbol, and the value is placed on the other side of the equals sign. This field processor is only applicable on the Subject header.

Example usage

Here is an example email where this processor is used in order send an assignee directive to JEMH Cloud.  For an extensive list of supported field types, please see Directives.

MIME-Version: 1.0 Subject: Subject of the email goes here #assignee=username From: bob@example.com To: jemhcloud@example.com Content-Type: text/plain; charset=UTF-8 This is the description/comment body of the email. It will not be considered as a directive by the processor!

Example Report

Here is the Report that is created when processing the above example email.

Example Issue page

Here is the issue page when the example email is processed by the Profile. This shows that the Assignee has been set:

Using Directives with spaces in the key

When using the Subject Field Processor, Keys with spaces (e.g. “Epic Link”) wont work. However, this can be solved by using an Alias of the Key that does not have spaces.

  1. Set up an Alias where the Alias is a custom field without a space and the value is a custom field. E.g. Below is an alias for the “Epic Link” field

 

  1. Once an Alias exists for the relevant Directive Key, you would then be able to use this Alias within the email to set this Field. Below, the Alias “epiclink” that was created is used as the key instead of “epic link”.

MIME-Version: 1.0 Received: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT) Date: Sun, 19 Jun 2011 17:42:26 +1200 Message-ID: BANLkTinB1mfSh+GwOXGNWoL4SyDvOpdBoQ@mail.gmail.com Subject: This is a starting email template, update as required #epiclink=red-1 From: admin@localhost To: catchemail@catch Content-Type: text/plain; charset=UTF-8 some content

Using Directives with spaces in the value

By default, a space character marks the end of a value only values of that do not contain spaces will work. For example, ‘#AKey=some value’ will populate the custom field ‘AKey’ with ‘some’. To process values that have spaces, enclose the value in double quotation marks (“ “). Note, apostrophes won’t work, only double quotation marks work:

  1. Create an email with a Subject Directive and enclose the value in double quotation marks.

MIME-Version: 1.0 Received: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT) Date: Sun, 19 Jun 2011 17:42:26 +1200 Message-ID: BANLkTinB1mfSh+GwOXGNWoL4SyDvOpdBoQ@mail.gmail.com Subject: This is a starting email template, update as required #directiveKey="this is a test for quotation marks" From: user1@test.com To: catchemail@catch Content-Type: text/plain; charset=UTF-8 some text

Some Fields only accept specific formats, for instance, the Labels field does not allow space characters therefore quotation marks won’t affect the final value of the Field.