...
Field processors by directive location in email
Subject | Body | Headers |
---|
#Prefix Field Processor | | |
...
Field Processor | Example | Notes |
---|
X-JEMH Header Field Processor | Code Block |
---|
X-JEMH-issueKey: JDP-19
X-JEMH-description: Hello, World! |
| |
#Prefix Field Processor | Code Block |
---|
#description="Hello, World!"
[#issueKey=JDP-19] |
| |
@Prefix Field Processor | Code Block |
---|
@description=Hello, World!
@issueKey=JDP-19 |
| Keys are prefixed with an at-symbol @ Directive must be located at the top of the email body There must be one newline between directive lines otherwise value is considered multi-line Multi-line fields will continue until end of body, or until another directive is found The end of the directives and start of actual body content is denoted by the use of one empty line between between Directives and Body
|
Colon Suffix Field Processor | Code Block |
---|
description:Hello, World!
issueKey:JDP-19 |
| Keys suffixed with a colon : Directive must be located at the top of the email body There must be one newline between directive lines Multi-line fields will continue until end of body, or until another directive is found
|
Nagios Field Processor | Nagios Field Processor Guide | |
Regexp Field Processor | Regexp Field Processor Guide | |
Enabling directive use with field processors
...