Versions Compared

Version Old Version 70 New Version Current
Changes made by

Dan Sparrow

Denny Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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]

  • This field processor parses the email subject only

  • String values are wrapped with quotation marks

@Prefix Field Processor

Code Block
@description=Hello, World!
@issueKey=JDP-19

This line is the start of the email text content. Note the blank separating line above.

  • 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

  • @Prefix cannot be used alongside Colon Suffix Field processor.

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

  • Colon Suffix cannot be used alongside At Prefix Field processor.

Nagios Field Processor

Nagios Field Processor Guide

Regexp Field Processor

Regexp Field Processor Guide

...

Type

Example Value

Checkboxes

custom checkboxes: option 1, Option 2

Custom Google Map Field

Not supported yet

Customer Request Type

Supported for create operation. JIRA raises an unexpected runtime exception on issue update.

Example:

@Customer Request Type=bsd/get-it-help

Read more about the value format in this wiki page.

Organizations

Allowed values are organization names or id (number). One or more organizations can be entered using comma separated values. 

@Organizations=Company A, 123

Date of First Response

Not supported yet

Date Picker

custom date picker: 29/7/2011

(Using default format of d/MM/yy)

or

custom date picker: 29-Jul-2011
custom date pickerFormat: dd-MMM-yyyy

(Second directive defines the format, it's the field name following 'Format')

Date Time Picker

custom date time picker: 29/7/2011 10:50 PM

(Using default format of dd/MM/yy h:mm a)

or

custom date time picker: 29-Jul-2011 10:50 PM
custom date time pickerFormat: dd-MMM-yyyy h:mm a

(Second directive defines the format, it's the field name following 'Format')

Global Rank

Not supported yet

Group Picker (multiple groups)

custom multi group picker: jira-team1-yoursite, jira-team2-yoursite

Group Picker (single group)

custom group picker: jira-team1-yoursite

Hidden Job Switch

Not supported yet

JIRA Agile Released Version History

Not supported yet

Job Checkbox

Not supported yet

Labels

custom labels: label1, label2

Multi Remote Object Link

Not supported yet

Number Field

custom number: 10

Project Picker (single project)

custom project picker: PKEY (Or name)

Radio Buttons

custom radio buttons: option1

Remote ObjectLink

Not supported yet

Remote System Reference

Not supported yet

Select List (cascading)

custom cascading select: Parent Option, Child Option

Select List (multiple choice)

custom multiple select: Option 1, option 2

Select List (single choice)

custom single list: Option 1

Tempo Account

Account: SomeAccountKey

Text Field (multi-line)

Code Block
my custom multline field: line 1
line 2
line 3

Text Field (read only)

custom text field read only: read only line

Text Field (single line)

custom text: only one line

Time In Status

Not supported yet

URL Field

custom url field: https://www.somehost.com/path

User Picker (multiple users)

custom multiple user picker: admin, someoneelse

User Picker (single user)

custom user picker: admin

UUID Field

Not supported yet

Version Picker (multiple versions)

custom multiple version: 2.1,2.3

Version Picker (single version)

custom single version: 2.1

Field processor ordering

Below is a list of the order in which certain Field processors are processed (If enabled):

  1. Basic Field Processor (Always on, default process behaviour).

  2. At (@) Prefix https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3486613507/At+Prefix?atl_f=PAGETREE

  3. Colon Suffix https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3706159105/Colon+Suffix+Mailform?atl_f=PAGETREE

  4. Subject Subject

  5. X-JEMH Mail header X-JEMH Header

  6. Regex Regexp

  7. Nagios Nagios Notifications

  8. Script Script Field Processor

Due to the above processing order, depending on the directives supplied and the resolution strategy selected, results may vary.

Filter by label
showLabelsfalse
max5
sortmodified
showSpacefalse
reversetrue
cqllabel in ( "directives" , "field-processors" ) and space = "JEMHC"