{"type":"doc","content":[{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{"maxLevel":{"value":"2"}},"macroMetadata":{"macroId":{"value":"29410161-7e4f-4ee1-a679-d9a935e98b2e"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}},"localId":"9aefd738-b42b-410d-883c-225f579568a4"}},{"type":"heading","attrs":{"level":1},"content":[{"text":"Introduction","type":"text"}]},{"type":"paragraph","content":[{"text":"Field Processors do nothing more than extract necessary information from an email by any means, in order to populate a Map of specified Keys used to create an Issue. The abstraction hopefully minimises the effort required to support different flavours of email source, without requiring multiple mailboxes or handlers configured. The aim is Low Management Overhead!","type":"text"}]},{"type":"paragraph","content":[{"text":"JEMH Field Processors that require directives to be supplied in the email body, (such as the Mailform, and @Prefix Field Processor) also require that the directives be supplied at the top of the email body before any other email content. Any directives separated by a new line will not be extracted by the Field Processor, e.g:","type":"text","marks":[{"type":"textColor","attrs":{"color":"#333333"}}]}]},{"type":"table","attrs":{"layout":"wide","width":960.0,"localId":"e7b7e261-e44d-48d2-9419-be7187154088"},"content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[493.0]},"content":[{"type":"paragraph","content":[{"text":"Input","type":"text"}]}]},{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[358.0]},"content":[{"type":"paragraph","content":[{"text":"Output","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[493.0]},"content":[{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nSubject: Subject of the email goes here\nFrom: test@example.com\nTo: changeme@thiswontwork.com\nContent-Type: text/plain; charset=UTF-8\n\npriority: 5\n\nassignee: username\n\nThis is the description/comment body of the email. It will not\nbe considered as a directive!\n\n","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[358.0]},"content":[{"type":"paragraph","content":[{"text":"Priority = 5","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[493.0]},"content":[{"type":"paragraph"},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nSubject: Subject of the email goes here\nFrom: test@example.com\nTo: changeme@thiswontwork.com\nContent-Type: text/plain; charset=UTF-8\n\nassignee: username\npriority: 5\n\nThis is the description/comment body of the email. It will not\nbe considered as a directive!","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[358.0]},"content":[{"type":"paragraph","content":[{"text":"Assignee = \"username\"","type":"text"}]},{"type":"paragraph","content":[{"text":"Priority = 5","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[493.0]},"content":[{"type":"paragraph"},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nSubject: Subject of the email goes here\nFrom: test@example.com\nTo: changeme@thiswontwork.com\nContent-Type: text/plain; charset=UTF-8\n\nassignee: username\n\nThis is the description/comment body of the email. It will not\nbe considered as a directive!\n\npriority: 5","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[358.0]},"content":[{"type":"paragraph","content":[{"text":"Assignee = \"username\"","type":"text"}]}]}]}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Enabling a Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"To enable a Field Processor need to toggle the relevant field Processor from a grey toggle to a Green toggle.","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":30.0},"content":[{"type":"media","attrs":{"width":910,"id":"106ef66e-5d46-4629-ac1c-00b57842d9e8","collection":"contentId-2850867","type":"file","height":478}}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"Once enabled you will then be able to see the Field Processor within the Summary section of the Profile. ","type":"text"},{"text":"Note","type":"text","marks":[{"type":"strong"}]},{"text":": Some Field Processors do not have any configuration options. There will be no Edit (Pen icon) button when there is no options.","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":30.0},"content":[{"type":"media","attrs":{"width":1169,"id":"431b69e4-6cc5-4c2a-ba62-f9319b522848","collection":"contentId-2850867","type":"file","height":711}}]},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"Once enabled you will then need to go to the Directives section and select a Directive Processing Behaviour. Current options are: On Create, On Comment or On Create or Comment. For more info about Directives see: ","type":"text"},{"text":"Use Directives","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/33357890"}}]}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":30.0},"content":[{"type":"media","attrs":{"width":988,"id":"d56dec33-cead-45fc-af05-ea870a6e4d68","collection":"contentId-2850867","type":"file","height":740}}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Standard Field Processors","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Colon Suffix (Mailform) Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"The Colon Suffix (Mailform) Field Processor enables JEMH to map values to Jira Fields with the notation “key:value”, where “key” is the name/id of the Field and “value” is the data that will populate the field. The Colon Suffix Field Processor can be used to set Fields during issue creation and update Fields on comment. Like the ","type":"text"},{"text":"@Prefix Field Processor","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/edit-v2/2850867#At-(%40)-Prefix-Field-Processor"}}]},{"text":", the Colon Suffix Field Processor is defined at the top of the email body, and is capable of multiline directives. Multi-line directives should only be included as the first of at-least 2 directives, otherwise JEMH will not know where the directive ends and the email begins.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Edge case: Colon Suffix Processor false Directive hits","type":"text"}]},{"type":"paragraph","content":[{"text":"The Colon Suffix Processor can falsely identify lines of text as a Directive if a colon is used within the first line of the email body, which will remove the falsely identified directive from the description/comment in the issue.","type":"text"}]},{"type":"paragraph","content":[{"text":"In the below example, “all of our servers went down at 8:30” is removed from the description:","type":"text"}]},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: \nSubject: This is a starting email template, update as required\nFrom: admin@localhost\nTo: catchemail@catch\nContent-Type: text/plain; charset=UTF-8\n\n\nall of our servers went down at 8:30\n\nThe quick brown fox jumped over the lazy dog and some text","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Stop the removal of text that has a colon","type":"text"}]},{"type":"paragraph","content":[{"text":"In ","type":"text"},{"text":"Profile > Configure > Email > Pre-processing, ","type":"text","marks":[{"type":"em"}]},{"text":"enabling the checkbox “Pre-validate Custom Field values”, will prevent the removal of the text “all of our servers went down at 8:30”.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Subject Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"This processor allows the subject line to be used as the vehicle for ","type":"text"},{"text":"Issue creation","type":"text","marks":[{"type":"annotation","attrs":{"annotationType":"inlineComment","id":"468b3ff4-df60-41c0-bfa8-22d72914c090"}}]},{"text":" ","type":"text"},{"text":"Directives","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850827"}}]},{"text":", i.e., using Subject Directives in emails that comment on existing issues will not work. Subject Field Processors follow the format “#key=value”, where “key” is a Field and “value” is the data to set to the Field. The Issue Summary will be set to whatever is left on the subject line that is not directives, both in terms of prefix and post-fix. Information in the middle will be lost, in the example below, the summary would end up being ","type":"text"},{"text":"This is prefix text This remaining text is also used","type":"text","marks":[{"type":"em"}]},{"text":".","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Simple example","type":"text"}]},{"type":"table","attrs":{"layout":"full-width","width":1800.0,"localId":"2f970291-3786-4047-b063-22276cc80290"},"content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[158.0]},"content":[{"type":"paragraph","content":[{"text":"Subject:","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[1461.0]},"content":[{"type":"paragraph","content":[{"text":"This is prefix text","type":"text","marks":[{"type":"strong"}]},{"text":" #project=jira #priority=trivial #watchers=user1,user2 ","type":"text"},{"text":"This remaining text is also used","type":"text","marks":[{"type":"strong"}]}]}]}]}]},{"type":"paragraph","content":[{"text":"Multiple values can of course be specified with comma delimiters.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Subject Field Processor is space delimited","type":"text"}]},{"type":"paragraph","content":[{"text":"Out of the box, the Subject Field Processor ends when white-space is found. If there is white-space in the key or the value, the Subject Field Processor won’t work as expected, for instance the following will fail to find the epic link and will only populate the Field ‘CustomTextField’ with the value 'A':","type":"text"}]},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: \nSubject: This is a starting email template, update as required #epic link=overarching task #CustomTextField=A single line text field\nFrom: admin@localhost\nTo: catchemail@catch\nContent-Type: text/plain; charset=UTF-8\n\nsome text","type":"text"}]},{"type":"paragraph","content":[{"text":"With some configuration changes, Subject Field Processors can contain white-space. For examples of Subject Field Processors containing white-space, see: ","type":"text"},{"text":"Using Directives with spaces in the key","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/edit-v2/2850867#Using-Directives-with-spaces-in-the-key"}}]},{"text":", ","type":"text"},{"text":"Using Directives with with spaces in the value: Double quotation marks","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/edit-v2/2850867#Using-Directives-with-spaces-in-the-value%3A-Double-quotation-marks"}}]},{"text":" and ","type":"text"},{"text":"Using Directives with spaces in the value: square brackets","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/edit-v2/2850867#Using-Directives-with-spaces-in-the-value%3A-square-brackets"}}]},{"text":".","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Using Directives with spaces in the key","type":"text"}]},{"type":"paragraph","content":[{"text":"Specific to the Subject Field Processor, keys with spaces e.g. “Epic Link” wont work, this can be solved using an ","type":"text"},{"text":"Alias","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3786342423"}}]},{"text":" without spaces in place:","type":"text"}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Set up an ","type":"text"},{"text":"Alias","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3786342423/Aliases#Creating-an-Alias"}}]},{"text":" where the Alias is a Custom Field without a space and the value is a Custom Field.","type":"text"}]}]}]},{"type":"paragraph","content":[{"text":"Alias:","type":"text"}]},{"type":"codeBlock","content":[{"text":"epiclink","type":"text"}]},{"type":"paragraph","content":[{"text":"Value:","type":"text"}]},{"type":"codeBlock","content":[{"text":"epic link","type":"text"}]},{"type":"orderedList","attrs":{"order":2},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"In the email, add the Subject Directive In the code-block below, the Alias “epiclink” that was created is used as the key instead of “epic link”.","type":"text"}]}]}]},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: BANLkTinB1mfSh+GwOXGNWoL4SyDvOpdBoQ@mail.gmail.com\nSubject: This is a starting email template, update as required #epiclink=red-1\nFrom: admin@localhost\nTo: catchemail@catch\nContent-Type: text/plain; charset=UTF-8\n\nsome content","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Using Directives with spaces in the value: Double quotation marks","type":"text"}]},{"type":"paragraph","content":[{"text":"By default, a space character marks the end of a value or, in other words, only values of Subject Field Processors 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:","type":"text"}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Create an email with a Subject Directive and enclose the value in double quotation marks.","type":"text"}]}]}]},{"type":"codeBlock","attrs":{"language":"none"},"content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: BANLkTinB1mfSh+GwOXGNWoL4SyDvOpdBoQ@mail.gmail.com\nSubject: This is a starting email template, update as required #SubjectFieldProcTest=\"this is a test for quotation marks\"\nFrom: user1@test.com\nTo: catchemail@catch\nContent-Type: text/plain; charset=UTF-8\n\nsome text","type":"text"}]},{"type":"panel","attrs":{"panelType":"warning"},"content":[{"type":"paragraph","content":[{"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.","type":"text"}]}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Using Directives with spaces in the value: square brackets","type":"text"}]},{"type":"paragraph","content":[{"text":"Enclosing a directive with square brackets, for example “[#key=value]”, will prevent white-space delimiting a value of a Text Field.","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Example","type":"text"}]},{"type":"orderedList","attrs":{"order":1},"content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Create an email with a Subject Directive and enclose the entire Subject Directive with square brackets.","type":"text"}]}]}]},{"type":"codeBlock","attrs":{"language":"none"},"content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: \nSubject: This is a starting email template, update as required [#AnotherCustomField=this is a custom field] #priority=5 \nFrom: admin@localhost\nTo: user2@test.com, catchemail@catch\nContent-Type: text/plain; charset=UTF-8\n\nsome text","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Limitations","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Specifying the Summary / Description fields in the Subject line is unlikely to lead to any useful outcome, don't bother.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"As only one line is available, who knows what limits an email client may pose on overall length.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Regexp Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"This field processor uses regular expressions in order to map values to issue fields. It can also be used to associate emails with issues, when a particular field value is found. For more information on this field processor, see ","type":"text"},{"text":"How Do I... Use Regexp Field Processor","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850891"}}]},{"text":".","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"CSV Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"You can use Excel or Open Office to populate a spreadsheet with issue creation information.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"CSV Format","type":"text"}]},{"type":"table","attrs":{"layout":"wide","width":960.0,"localId":"3b376798-e31e-4839-8722-f9143adba461"},"content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[149.0]},"content":[{"type":"paragraph","content":[{"text":"Line 1 of body","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[810.0]},"content":[{"type":"paragraph","content":[{"text":"Must contain all required issue information, one entry per cell, e.g. 'project', 'priority' etc","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1,"colwidth":[149.0]},"content":[{"type":"paragraph","content":[{"text":"Line 2+ of body","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[810.0]},"content":[{"type":"paragraph","content":[{"text":"Contains the values for each of the issue properties defines in line 1","type":"text"}]}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Example","type":"text"}]},{"type":"table","attrs":{"layout":"full-width","width":1800.0,"localId":"c4d40d38-1caf-4e88-aad9-c4b8c5909aa4"},"content":[{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[907.0]},"content":[{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"codeBlock","attrs":{"language":"plaintext"},"content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: \nSubject: This is a starting email template, update as required\nFrom: \"Andy Brook\" \nTo: changeme@thiswontwork.com\nContent-Type: text/plain; charset=UTF-8\n\n\"project\",\"reporter\",\"priority\",\"issueType\",\"summary\", \"epic name\", \"epic link\", \"epic colour\"\n\"test\",\"admin\",\"medium\",\"bug\",\"summary text 1\",,,\n\"test\",\"admin\",\"highest\",\"epic\",\"summary text 2\", \"epic name here\",,\"ghx-label-4\"\n\"test\",\"admin\",\"lowest\",\"bug\",\"summary text 3\",,\"epic name here\",","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[713.0]},"content":[{"type":"paragraph","content":[{"type":"hardBreak"}]},{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"__confluenceADFMigrationUnsupportedContentInternalExtension__","text":"","parameters":{"cxhtml":"

Line	Explanation
9	Defining the headers that we want to give values to
10	Creates a bug issue with "medium" priority and summary text "summary text 1" and assigns to username "admin"
11	Creates an Epic with name "epic name here" and the 4th colour pre-set
12	Creates a bug issue with priority "lowest" and links to epic created in line 11

","nestedContent":{"type":"doc","content":[{"type":"table","content":[{"type":"tableRow","content":[{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Line","type":"text"}]}]},{"type":"tableHeader","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Explanation","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"9","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Defining the headers that we want to give values to","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"10","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Creates a bug issue with \"medium\" priority and summary text \"summary text 1\" and assigns to username \"admin\"","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"11","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Creates an Epic with name \"epic name here\" and the 4th colour pre-set","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"12","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1},"content":[{"type":"paragraph","content":[{"text":"Creates a bug issue with priority \"lowest\" and links to epic created in line 11","type":"text"}]}]}]}]}],"version":1},"reason":"A table in a table cell can't be created or edited in the new editor."}}},{"type":"paragraph","content":[{"type":"hardBreak"}]}]}]}]},{"type":"panel","attrs":{"panelType":"success"},"content":[{"type":"heading","attrs":{"level":3},"content":[{"text":"Use of Attachments","type":"text"}]},{"type":"paragraph","content":[{"text":"Use of a CSV attachment of the above format is supported. In order to 'activate' this feature, the first line of the email body must start with exactly: ","type":"text"},{"text":"useAttachmentFilename=true","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"panel","attrs":{"panelType":"success"},"content":[{"type":"heading","attrs":{"level":3},"content":[{"text":"Using double quotes and commas in field values","type":"text"}]},{"type":"paragraph","content":[{"text":"Want to use double quotes in the field values? As the CSV field processor is expected these to be used to contain fields and values it gets a little tricky. The solution is to double up quotes that are ","type":"text"},{"text":"inside","type":"text","marks":[{"type":"em"}]},{"text":" values. For example:","type":"text"}]},{"type":"codeBlock","content":[{"text":"\"This is the value for an issue \"\"description\"\". This is the second sentence of the description.\"","type":"text"}]},{"type":"paragraph","content":[{"text":"Commas are seen, naturally, as value separators. If you wish to use them in a field such as the description, you can do so by using the ASCII code for a comma:","type":"text"}]},{"type":"codeBlock","content":[{"text":",","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"At (@) Prefix Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"This field processor uses content in the format \"@key=value\". The key is prefixed with the \"at\" symbol (@) and the value is placed on the other side of the equals sign. Here is an example email where the @prefix field processor is being used to send an assignee directive. For a list of supported field types, please see this wiki page: ","type":"text"},{"text":"Supported fields for use with Directives","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850827"}}]},{"text":".","type":"text"}]},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nSubject: Subject of the email goes here\nFrom: test@example.com\nTo: changeme@thiswontwork.com\nContent-Type: text/plain; charset=UTF-8\n\n@assignee=username\n\nThis is the description/comment body of the email. It will not\nbe considered as a directive!","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"XML Format Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"Issue attributes can be provided in an email with XML formatting if required. It uses XStream to read the data, hence its verbosity. Its parse priority is 5000.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Code to generate the XML","type":"text"}]},{"type":"paragraph","content":[{"text":"If you don't want to generate the XML code yourself you can make use of the JEMH Jar itself, you'll also need the XStream library to make use of this.","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":5},"content":[{"text":"Example code for generating the correct format","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","attrs":{"language":"java"},"content":[{"text":"private void doit()\n{\nJemhXmlPayload payload=new JemhXmlPayload();\nList entries=payload.getJemhPayload();\ncreateSimpleEntry(entries, \"priority\", \"high\");\ncreateSimpleEntry(entries, \"reporter\", \"userX\");\ncreateSimpleEntry(entries, \"assignee\", \"admin\");\ncreateSimpleEntry(entries, \"watchers\", \"user1\",\"user2\",\"user3\");\ncreateSimpleEntry(entries, \"description\", \"this is the body of the email\");\ncreateSimpleEntry(entries, \"summary\", \"this is the summary of the email\");\n\t\t\nXStream xs=new XStream();\nxs.alias(\"JemhXmlData\",JemhXmlPayload.class);\t\t\nxs.alias(\"Entry\", Entry.class);\nString xml=xs.toXML(payload);\nSystem.out.println(\"XML:\\n\"+xml);\n}\n\nprivate void createSimpleEntry(List entries, String key, String... value )\n{\nList values=new ArrayList();\nfor (int i = 0; i < value.length; i++)\n {\n\tvalues.add(value[i]);\n }\nentries.add(new Entry(key,values));\n}","type":"text"}]},{"type":"heading","attrs":{"level":5},"content":[{"text":"Parsing of XML payload","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","attrs":{"language":"java"},"content":[{"text":"XStream xs = new XStream();\nxs.alias(\"JemhXmlData\", JemhXmlPayload.class);\nxs.alias(\"Entry\", Entry.class);\nJemhXmlPayload xmlPayload = (JemhXmlPayload) xs.fromXML(body);","type":"text"}]},{"type":"heading","attrs":{"level":5},"content":[{"text":"Example email body content to send to JEMH","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n \n \n priority\n \n high\n \n \n \n reporter\n \n userX\n \n \n \n assignee\n \n admin\n \n \n \n watchers\n \n user1\n user2\n user3\n \n \n \n description\n \n this is the body of the email\n \n \n \n summary\n \n this is the summary of the email\n \n \n \n","type":"text"}]},{"type":"paragraph"},{"type":"heading","attrs":{"level":2},"content":[{"text":"Default 'Basic' Mail Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"This processor will attempt to create issues if no other configured handler can. It doesn't have the smarts that other handlers have and is a 'translated' version of the original Atlassian mail processor.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Script Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"When JEMH Processes messages, the content (subject/body) can be subjected to Field Processors, which are specialised parsers. Other examples of Field Processors are the AtPrefix format, which parses out ","type":"text","marks":[{"type":"textColor","attrs":{"color":"#333333"}}]},{"text":"@key=value","type":"text","marks":[{"type":"em"}]},{"text":" combinations from the email body lead in. These keys are ","type":"text","marks":[{"type":"textColor","attrs":{"color":"#333333"}}]},{"text":"Supported Fields for use with Directives","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850827/Supported+Fields+for+use+with+Directives"}}]},{"text":", and allow Email content to drive issue updated during create and comment, even workflow transitions. The script field processor is the final piece in the puzzle for customisation processing of content, until now, new 'custom' processing could only be achieved with add-ons for JEMH, which are a technology hurdle too far for most. With the new Script Field Processor, basic knowledge of JavaScript and this how to guide will be enough to have you running in no time!","type":"text","marks":[{"type":"textColor","attrs":{"color":"#333333"}}]}]},{"type":"paragraph","content":[{"text":"Due to the extensive nature of this Field Processor, there is a full article available about it here: ","type":"text"},{"text":"Use Script Field Processor","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/227115013"}}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"X-JEMH Header","type":"text"}]},{"type":"paragraph","content":[{"text":"This field processor will check for headers that use X-JEMH at the begging of the header and will then set the related field with the header value. e.g. “X-JEMH-priority: critical”","type":"text"}]},{"type":"paragraph","content":[{"text":"Example email:","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","content":[{"text":"MIME-Version: 1.0\nReceived: by 10.223.112.12 with HTTP; Sat, 18 Jun 2011 22:42:26 -0700 (PDT)\nDate: Sun, 19 Jun 2011 17:42:26 +1200\nMessage-ID: \nX-JEMH-priority: low\nX-JEMH-project: Service Project\nX-JEMH-assignee: admin\nX-JEMH-issueType: bug\nSubject: This is a starting email template, update as required\nFrom: admin@localhost\nTo: mailbox@localhost\nContent-Type: text/plain; charset=UTF-8\n\nThis is the email body","type":"text"}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Specialist Field Processors","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Nagios Field Processor","type":"text"}]},{"type":"paragraph","content":[{"text":"The Nagios Field Processor has been developed to enable JIRA to be a sink for automatic notifications, but not just sink them, to correlate and close them as required. This results in a condensing of notifications onto one JIRA issue, per related notification, with no need to manually go and close them if they resolve themselves/are resolved. For more information on the configuration of this field processor, see ","type":"text"},{"text":"Use Nagios Field Processor","type":"text","marks":[{"type":"link","attrs":{"href":"https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850892"}}]},{"text":".","type":"text"}]},{"type":"paragraph","content":[{"text":"This Field Processor uses ","type":"text"},{"text":"JQL","type":"text","marks":[{"type":"link","attrs":{"href":"https://confluence.atlassian.com/jiracore/blog/2015/07/search-jira-like-a-boss-with-jql"}}]},{"text":" to find fuzzy matches, it then further refines this list to an exact Subject match, guaranteeing correct associations. See ","type":"text"},{"text":"an example issues life-cycle","type":"text","marks":[{"type":"link","attrs":{"href":"/wiki/pages/resumedraft.action?draftId=2850867"}}]},{"text":" with appending and closure...","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Format","type":"text"}]},{"type":"paragraph","content":[{"text":"Nagios has templated subject lines as well as body content. This handler only interrogates the Subject, there are a variety of formats, for example, the standard Ubuntu distribution generates:","type":"text"}]},{"type":"codeBlock","content":[{"text":"From nagios@trippy Fri Jan 29 11:50:54 2010\nReturn-Path: \nX-Original-To: nagios@jira.myco.net\nDelivered-To: nagios@jira.myco.net\nReceived: by trippy (Postfix, from userid 117)\n\tid BFAE31E8C; Fri, 29 Jan 2010 11:50:54 +0000 (GMT)\nTo: nagios@jira.myco.net\nSubject: ** PROBLEM Service Alert: localhost/SSH is CRITICAL **\nMessage-Id: <20100129115054.BFAE31E8C@trippy>\nDate: Fri, 29 Jan 2010 11:50:54 +0000 (GMT)\nFrom: nagios@trippy\n\n***** Nagios *****\n\nNotification Type: PROBLEM\n\nService: SSH\nHost: localhost\nAddress: 127.0.0.1\nState: CRITICAL\n\nDate/Time: Fri Jan 29 11:50:54 GMT 2010\n\nAdditional Info:\n\nConnection refused\n","type":"text"}]},{"type":"paragraph"},{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":50.0},"content":[{"type":"heading","attrs":{"level":3},"content":[{"text":"Format","type":"text"}]},{"type":"paragraph","content":[{"text":"Nagios has templated subject lines as well as body content. This handler only interrogates the Subject, there are a variety of formats, for example, the standard Ubuntu distribution generates:","type":"text"}]},{"type":"codeBlock","content":[{"text":"From nagios@trippy Fri Jan 29 11:50:54 2010\nReturn-Path: \nX-Original-To: nagios@jira.myco.net\nDelivered-To: nagios@jira.myco.net\nReceived: by trippy (Postfix, from userid 117)\n\tid BFAE31E8C; Fri, 29 Jan 2010 11:50:54 +0000 (GMT)\nTo: nagios@jira.myco.net\nSubject: ** PROBLEM Service Alert: localhost/SSH is CRITICAL **\nMessage-Id: <20100129115054.BFAE31E8C@trippy>\nDate: Fri, 29 Jan 2010 11:50:54 +0000 (GMT)\nFrom: nagios@trippy\n\n***** Nagios *****\n\nNotification Type: PROBLEM\n\nService: SSH\nHost: localhost\nAddress: 127.0.0.1\nState: CRITICAL\n\nDate/Time: Fri Jan 29 11:50:54 GMT 2010\n\nAdditional Info:\n\nConnection refused\n","type":"text"}]},{"type":"paragraph","content":[{"type":"hardBreak"}]}]},{"type":"layoutColumn","attrs":{"width":50.0},"content":[{"type":"heading","attrs":{"level":3},"content":[{"text":"Logic","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"center"},"content":[{"type":"media","attrs":{"width":820,"id":"ba41b90a-b6b5-4087-b348-9cae333f3ed0","collection":"contentId-2850867","type":"file","height":465}}]},{"type":"paragraph"}]}]},{"type":"paragraph","content":[{"text":"The keywords (e.g. CRITICAL) are used to group related messages (i.e. expectation is that the rest of the information is the same), you can configure (currently limited to 10) related state groups. See the ","type":"text"},{"text":"Nagios Configuration","type":"text","marks":[{"type":"link","attrs":{"href":"/wiki/spaces/JEMH/pages/2850881#JEMHUsageGuide-JEMHUsageGuide-NagiosFieldProcessor"}}]},{"text":" of the Usage Guide.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Third Party Field Processor Enablement","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Enabled third party Field Processors","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"This is a list of Third Party Field Processors that have been added to JEMH/Jira. To select/deselect the relevant processor you will have to use ","type":"text"},{"text":"Ctrl","type":"text","marks":[{"type":"strong"}]},{"text":" + ","type":"text"},{"text":"Click","type":"text","marks":[{"type":"strong"}]},{"text":".","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Indicate active Field Processor/Profile","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"This will prefix the description/comment with text identifying the Field Processor that was used and from what Profile.","type":"text"}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Related Articles","type":"text"}]},{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"contentbylabel","parameters":{"macroParams":{"showLabels":{"value":"false"},"max":{"value":"5"},"showSpace":{"value":"false"},"cql":{"value":"label = \"field-processors\" and space = \"JEMH\""}},"macroMetadata":{"macroId":{"value":"742f8d97-1891-4a7c-810e-b9bf873a95b4"},"schemaVersion":{"value":"4"},"title":"Filter by label (Content by label)"}},"localId":"20b0a5af-49b4-4054-9507-94eb4f920638"}}],"version":1}

Browser not supported