Fields

System Fields

Name	Type	Explanation	Example	Annotation
Reporter, Assignee	String	User field containing a username, e.g., {Reporter} represents the username of the issue's Reporter field.	{Reporter} = "admin"	Anonymous is represented by ""
Environment, Description, Summary	String	Text field, e.g., {Summary} contains the text entered in the issue's Summary field.	{Summary} = "Summary"
Due Date, Created, Updated	Date	Date field, e.g., {Due Date} contains the date entered in the issue's Due Date field.	{Due Date} = 24.12.2012
Original Estimate, Remaining Estimate, Time Spent	Timespan	Timespan field, e.g., {Original Estimate} contains the timespan entered in the issue's Original Estimate field.	{Original Estimate} = 4w 5d 6h	If nothing is entered in the field, Workflow Enhancer for Jira returns 0min (i.e., {...} = 0min)
Σ Original Estimate, Σ Remaining Estimate, Σ Time Spent	Timespan	Time span field, e.g., {Σ Original Estimate} contains the sum of the Original Estimates of the issue's subtasks.	{Σ Original Estimate} = 1w 4d 3h	if nothing is entered in the field, Workflow Enhancer for Jira returns 0min (i.e., {...} = 0min)
Project	String	{Project} contains the issue's Project name.	{Project} = "Rocket"
Priority	String	{Priority} contains the text of the issue’s Priority field.	{Priority} = "Major"
Status	String		{Status} = "In Progress"
Resolution	String		{Resolution} = "Resolved"
Issue Type	String		{Issue Type} = "Bug"
Key	String	{Key} contains the issue’s key.	{Key} = "ROCKET-1"
Issue Links	String	{Linked Issues} <=> "Passive: LinkType % IssueKey $ ... $ LinkType % IssueKey Aktive: LinkType % IssueKey $ ...$ LinkType % IssueKey"	Linked exactly with ROCKET-1 as a Blocker and ROCKET-42 as a Cloner: `{Linked Issues} = "Passive: Blocks % ROCKET-1 Aktive: Cloners % ROCKET-42"` Linked exactly with ROCKET-42 as Cloner `{Linked Issues} = " Aktive: Cloners % ROCKET-42"` Has to have at least one active Link of type Relation: `{Linked Issues}=/ Aktive: .Relation./`	Jira’s default link types are Blocks, Cloners and Duplicate. Note the space before “Aktive“ and the spelling of “Aktive“. Set the log level to DEBUG and check in the logs as this syntax is not really easy to handle.
Labels	String	Returns the array of labels as String in alphabetical order; e.g., [label1, label2, label3]	`{labels} = "[labelX]"` for a single label or `{labels} = "[]"` for no label. `{labels} = /.labelX./` if you want to check if a version called "labelX” is set and you do not care about other versions.	Use regular expressions to check for one label among several.
Fix Version/s, Affects Version/s	String	Returns the array of versions as String in alphabetical order; e.g., [version1, version2, version3]	`{Fix Version/s} = "[versionX]"` for a single version or `{Fix Version/s} = "[]"` for no version. `{Fix Version/s} = /.versionX./` if you want to check if a version called "versionX” is set and you do not care about other versions.	Use regular expressions to check for one version among several.
Components	String	Returns the Array of components as String in alphabetical order; e.g., [component1, component2, component3]	`{Components} = "[componentX]"` for a single component or`{Components} = "[]"` for no component. `{Components} = /.componentX./` if you want to check if a component called "componentX” is set and you do not care about other components.	Use regular expressions to check for one component among several.
Transition Comment	String	Returns the comment added in the transition as a String.		Only useful for post functions and validators if a screen is shown during the transition.

Jira fields (written as `{field_id}`) may themselves contain a special value. Therefore if a field contains a value such as `1h 30min`, it will automatically be parsed as a timespan. This also allows for a chain of field identifiers (by putting the identifier of another field in a field). An application might be that the first element of the chain is set as a post-function to dynamically change the behavior of the condition/validator depending on the steps in the workflow we have visited.

To make the field value non-evaluating (i.e not evaluating chained field identifiers within the field), use double brackets (e.g. {{description}})

Please compare Jira fields always with English field values, e.g., {Resolution} = "Resolved".

Fields of type String only allow String comparisons. So, especially the order operations <, <=, >=, and > often do not make sense, e.g., in the case of priority {Priority} > "A String which begins with the letter a" always evaluates to "True".

You can use both, field names in your local language as well as english lower-case names, e.g., in German {resolution} and {Lösung} both refer to the resolution while {Resolution} tries to evaluate a custom field.

Custom Fields

Use field id to include custom fields in an expression: {customfield_123}

While using custom field names directly works for expression evaluation, it does not work for cloud migration.

Type	Explanation	Annotation
Date Picker	{Date Picker} represents the picked date as a date value.	e.g., `{Date Picker} = 25.09.2012 00:00` if you picked 25/Sep/2012 in the issue's Date Picker field or {Date Picker} = "" if you want to check that the date picker is empty
Version Picker	{Single Version Picker} represents all picked versions of the issue as a comma and space separated String.
Single Version Picker	{Version Picker} represents the picked version as a String.
Project Picker	{Project Picker} represents the picked project name as a String.
User Picker	{User Picker} represents the picked username as a String.
Multi User Picker	{Multi User Picker} represents all picked usernames in a comma and space separated String.	e.g., `{Multi User Picker} = "username1, username2"` if you picked user1 and user2 in the issue's Multi User Picker field.
Group Picker	{Group Picker} represents the picked group name as a String.
Multi Group Picker	{Multi Group Picker} represents all picked group names in a comma and space separated String.	e.g., `{Multi Group Picker} = "jira-developers, jira-users"` if you picked these groups in the issue's Multi Group Picker field
Number Field	{Number Field} represents the entered number as a Float value.	e.g., `{Number Field } = "3.14"` if you entered 3.14 in the issue's Number Field field
Free Text Field	{Free Text Field} represents the entered text as a String.	e.g., `{Free Text Field} = "all work and no play makes Jack a dull boy"` if you entered all work and no play makes Jack a dull boy in the issue's Free Text field
Text Field	cf. Free Text Field
Label	{Labels} represents all labels, which are set for this issue, as a String.	e.g., `{Label} = "label1, label2, label3"` if you set these labels to the issue. Note that Jira might sort the labels so that "label1, label2" = "label2, label1"
Date Time	{Date Time} represents the picked point in time as a Date value.	e.g., `{Date Time} = 24.12.2012 15:45` if you picked this date time in the issue's Date Time field.
URL Field	{URL Field} represents the entered URL as a String.	e.g., `{URL Field} = "http://en.wikipedia.org/wiki/Uniform_Resource_Locator"`
Import Id	NOT SUPPORTED
Read only Text Field	NOT SUPPORTED
Cascading Select	{Cascading Select} represents the selected options as a String in the same format as Atlassian's `.toString()` method for Cascading Select fields: `null=PARENT, 1=CHILD` `null=PARENT` if no child value is selected `""` if no value is selected	e.g., `{Cascading Select} = /null=., 1=./` to ensure both values are set
Bug Import ID	NOT SUPPORTED
Multi Select	{Multi Select} represents the selected options as a comma and space separated String.
Radio Buttons	{Radio Button Field} represents the selected option as a String.
(Multi) Checkbox	{Checkbox} represents the selected options as a comma and space separated String.
Select List	{Select List} represents the selected option as a String.
Hidden Job Switch	NOT SUPPORTED