Versions Compared

Old Version 17

changes.mady.by.user Phil Evans

Saved on

compared with

New Version Current

changes.mady.by.user Yevgenia Suleimanova

Saved on

Key

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

...

Field

Description/notes

Use in create

Use in comment

custom-field

Custom fields can be manipulated in two ways:

  • The custom field name. If values for fields can be represented as a string. Tested with Labels, e.g. "Labels: sentByEmail". Note to be careful naming custom fields with default field names, for example assignee is a default field.

  • Custom field ids can be used as per example:

    • customfields_<customfield id>

(tick)

(tick)

project

numeric (e.g. 10001), textual name (e.g. Support) or project key (e.g. SPP). Only required if email to: address is not a known project key

(tick)

(error)

priority

numeric (e.g. 4) or text name (e.g. critical)

(tick)

(tick)

issueType

numeric (e.g. 12) or text name (e.g. Feature Request)

(tick)

(tick)

issueType.status

Status
colourRed
titlesince 3.3.56

Info

Requires an issueType directive to be defined.

numeric (e.g. 6) or text name (e.g. Closed)

It’s possible to migrate an existing Issue Type with a status when this directive is used in conjunction with the issueType directive.

For example (in the @ prefix field processor):
@issueType=Task
@issueType.status=Closed

Note

Status migration will only be processed during commenting. If an invalid status is found or issue failed to transition to the supplied Status value; then issue will proceed as original issue type and workflow state.

(error)

(tick)

components

A CSV capable field. Can be numeric (e.g. 100020) or textual name (e.g. My Magic Component)

(tick)

(tick)

viewable

String value matching a group or role name, used to restrict the visibility of comments

(tick)

(tick)

environment

String

(tick)

(error)

reporter

userid or email address of given user in JIRA

(tick)

(tick)

assignee

userid or email address of given user in JIRA, who is 'assignable'

(tick)

(tick)

summary

String (single line)

(tick)

(tick)

description

String (multiple lines)

(tick)

(tick)

watchers

Comma Separated Variable list of userid's, in Jira

(tick)

(tick)

dueDate

Users can override the default (ISO standard) SimpleDateFormat string yyyy-MM-ddTHH:mm:ssZthrough the 'dueDateFormat' field (e.g. dd-MMM-yyyy enables dates like 12-May-2009.  If the user does not provide a dueDateFormat directive, the system default (in jira-application.properties) under the key jira.date.picker.java.format will be used as a fallback

Note

From version 2.5.1 date values supplied by email directives are locale sensitive. For example, a Jira user with Spanish set as their profile language should send date values such as 3/ene/19 instead of 3/jan/19.

Prior to 2.5.1, date values should be sent using the system default locale.

(warning) Further complication, the date format supported in JDK is different in JDK11, see:

(tick)

(tick)

workEstimate

of format 1w7d12h30m, or any derivative (info) JIRA 6 requires spaces between values. When supplied in the subject it needs quoting like: #workEstimate="1w 2d 3h"

(tick)

(tick)

linkto

Issue Linking more information on Issue Links here: https://confluence.atlassian.com/adminjiraserver/configuring-issue-linking-938847862.html ,

Format

Legend

  • direction type = to/from

  • destinationIssue = issue you want the property to apply to

  • sourceIssue = issue being processed

  • linkTypeProperty = outward/inward/name value

Code Block
directionType:destinationIssue/linkTypeProperty

Examples

to

to:ABC-101/duplicate

from

from:XYZ-123/relates

to+from

to:ABC-101/duplicate,from:XYZ-123/relates

multiple links

to:ABC-101/duplicate,from:XYZ-123/relates,from:XYZ-124/is blocked by,to:XYZ-125/blocks

(tick)

(tick)

fixVersions

1.3,2.1

(tick)

(tick)

affectsVersions

1.0,1.1,2.0

(tick)

(tick)

vote

true (only value to make sense/false)

(tick)

(tick)

securityLevel

Long value, e.g. 12345.

(tick)

(tick)

...