Content Comparison

Values are considered as CSV where mulitple values are possible (eg selects, multi picker fields), in such cases, comma ' , ' cannot form part of values to be set.

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>

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

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

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

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

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

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

String

userid or email address of given user in JIRA

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

String (single line)

String (multiple lines)

Comma Separated Variable list of userid's, in Jira

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

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

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

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

1.3,2.1

1.0,1.1,2.0

true (only value to make sense/false)

Long value, e.g. 12345.

Required when creating an issue of type "Epic"

Required in order to link when linking an issue to a parent Epic.   The To link to an epic, the value used is the name “epic name” or the issue-key of the epic you are linking it to.

The colour pre-set used for the Epic.  The values are ghx-label-1 to ghx-label-9.