Values | Documentation

Workflow Enhancer for Jira let’s you compare the value of a field or macro against different types of values, listed below:

String

	Example
any String has to be enclosed by " (quotation marks)	`"String"`

Regular Expression

	Example
any regular expression has to be enclosed by / (forward slashes)	`/ab/`
matches the preceding element zero or more times	`/a*/` = {ε,a,aa,aaa,aaaa,...}
+ matches the preceding element one or more times	`/a+/` = {a,aa, aaa,aaaa,...}
? matches the preceding element zero or one time	`/a?/` = {ε,a}
( ) defines subexpression	`/(ab)+/` = {ab,abab,abab,ababab,...}
{n} matches the precending element exactly n times	`/a{3}/` = {aaab}
{min, max} matches the preceding element at least min and at most max times	`/a{2,4}/` = {aa,aaa,aaaa} `/a{1,}/` = /a+/ = {a,aa,aaa,...} `/a{ ,5}/` = {ε,a,aa,aaa,aaaa,aaaaa}

In the examples above ε always stands for the empty word. For example, in the case of /a?/ there can be either one "a" or no "a".

Field interpolation in Regular Expression

For your field to be evaluated in regex, you must use the {field_id} notation, as expressions of the type {field_name} will not be evaluated. For custom fields, this will be of the form {customfield_123}, for system fields, it is generally the name in lowercase with spaces and special characters removed, as per the table below. Note that, when inserting a field using the UI, it will show the {field_name} by default, and this must be converted to {field_id}.

	Example
A field in a regular expression is replaced by its value (as string)	`/{description}/` = `abc` (when the value of description is abc)
The value of the field is evaluated	`/{description}/` = `Max` (when `{description} = "{assignee}"` and `{assignee} = "Max"`
Use double curry brackets (`{{`) to skip the evaluation of a field value	`/{{description}}/` = `{assignee}` (when `{description} = "{assignee}"` and `{assignee} = "Max"`)
Custom fields are supported	`/{customfield_123}/`
Use `\` to escape the interpolation (only works in regex, not in the field’s value)	`/\{description\}/` becomes regex `/\{description\}/`, matches the string `{description}`
Use `\Q` and `\E` to escape a sequence	`/\Q{description}.\E/` becomes the same regex, and matches the string `{description}.`

Both left and right curry braces need to be escaped. Regex like /\{abc}/ will not work.

System Field Name in English	Field ID
Description	description
Summary	summary
Issue Type	issuetype
Priority	priority
Resolution	resolution
Version/s	versions
Fix Version/s	fixVersions
Component/s	components
Labels	labels
Environment	environment
Linked Issues	issuelinks
Attachment	attachment
Assignee	assignee
Reporter	reporter
Due Date	duedate
Time Tracking	timetracking
Security Level	security

Date

	Example
Date pattern: dd.mm.yyyy hh:mm	`24.12.2012 15:30`
Time is optional	`24.12.2012`

The maximum date value is 31.12.2099 23:59.

Timespan

	Example
Labor Timespan pattern: n₁w n₂d n₃h n₄min , where n₁, n₂, n₃, n₄ are non negative integers	`12w 13d 5h 3min` = 12 labor weeks 13 labor days 5 hours and 3 minutes
Real Timespan pattern: n₁W n₂D n₃H n₄MIN , where n₁, n₂, n₃, n₄ are non negative integers	`12W 13D 5H 3 MIN` = 12 weeks 13 days 5 hours and 3vminutes
If a component is 0, it can be omitted	`0w 5d 3h 0min` = 5d 3h
It is not possible to change the order	Wrong: `5d 8w` Right: 8`w 5d`

Workflow Enhancer for Jira works with the time tracker of your Jira such that a timespan of Jira is automatically a labor timespan. This also means that a date and timespan field cannot be added.
If the time tracker is disabled, we have 1 day = 8 hours and 1 week = 5 days.

So, if your Jira time tracker settings are 1 labour day = 24 hours and 1 labor week = 7 labor days, labor timespan and real timespans are the same.

Float

	Example
Pattern: d+(.d)? or d(.d+)? where d is an integer	`3.14`

The Workflow Enhancer for Jira float data type works with negative values, but the parser does not support unary operations.