Expressions

Number Expressions

Number expressions are a sequence of digits that result in a number context-item.

Text Expressions

Text expressions are text content enclosed in quotation marks that result in a text context-item.

Composite Expression Operators

Composite expressions are a combination of two separate expressions using an operator, the result is a single context-item.

The possible operators are:

Operator =

Compares the two expressions for equality, the two expressions must both be either a number or a text. The result expression is a boolean context-item.

Operator <>

Compares the two expressions for inequality, the two expressions must both be either a number or a text. The result expression is a boolean context-item.

Operator +

Combines the two expressions using addition semantics, the two expressions must both be either a number or a text. The result expression is either a number or a text depending on the expression context-items.

Operator <

Compares the two expressions with less semantic, the two expressions must be a number. The result expression is a boolean context-item.

Operator >

Compares the two expressions with greater semantic, the two expressions must be a number. The result expression is a boolean context-item.

Expression "."

The dot expression refers to a path element on the current context-item.

Please note that the path can also be empty, in this case the default value of a context-item is substituted.

For example if the context-item is a JIRA issue then the following expression

will evaluate to the JIRA issue key and will be substituted in the Word contents with e.g.

Expression "baselines" Data center only

The baselines expression will be evaluated to result in a Baselines context-item for further use in expressions.

Expression "currentIndex"

The currentIndex expression can be used to determine the current iteration of a loop statement.
The expression evaluates to a number context-item starting at zero for the first iteration of a loop. With each iteration number is increased by one. 
This expression can be used with the each-, filter- and jql-statement. 

Example:

Expression "durationDays" Data center only

The durationDays expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation of the fractional day value like

Expression "durationHours" Data center only

The durationHours expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation of the fractional hour value like

Expression "durationJira" Data center only

The durationJira expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation in the JIRA duration format # weeks , # day, # hours, # minutes

Expression "durationShortJira" Data center only

The durationShortJira expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation in the JIRA short duration format # w , # d, # h, # m

Expression "durationTimespan" Data center only

The durationTimespan expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation in format HH:MM:SS

Expression "durationWeeks" Data center only

The durationWeeks expression itself must be followed by an expression evaluating to a duration context-item such as a JIRA issue estimated value.

Example : 

Will result in a text representation of the fractional week value like

Expression "exportLongDate" Data center only

The exportLongDate expression will be evaluated to a String context-item of the date and time representation at which the export has been performed.

Expression "exportShortDate" Data center only

The exportShortDate expression will be evaluated to a String context-item of the date representation at which the export has been performed.

Expression "metadata"

The metadata expression will be evaluated to result in a Metadata context-item for further use in expressions.
This expression enables the output of template information.

Expression "projects" Data center only

The projects expression will be evaluated to result in a Projects context-item for further use in expressions.

Expression "property" Data center only

The property expression will be evaluated to result in a Property context-item for further use in expressions.

Example:

Expression "selectedBaseline" Data center only

The selectedBaseline expression may contain a Baseline context-item that is passed to the template execution by a user selection.

If no baseline is selected upon export, the selectedBaseline evaluation results in an empty text. To use this expression, you must be in the baseline details of the baseline to be exported.

Expression "selectedProject"

The selectedProject expression may contain a Project context-item that is passed to the template execution by a user selection.

If no project tree is selected upon export (e.g exporting outside of the project tree), the selectedProject evaluation results in an empty text.

Expression "selectedFilter" Data center only

The selectedFilter expression may contain a text context-item of the JIRA filter that has been passed to the template generation by a user selection.

If no filter is applied to the project tree upon export, the selectedFilter evaluation results in an empty text. This applies also to an advanced filter selection with a JQL.

Expression "selectedTreeFolder"

The selectedTreeFolder expression may contain a Folder context-item that is passed to the template generation by a user selection.

If no folder is selected upon export, the selectedTreeFolder evaluation results in an empty text.

Expression "selectedTreeIssue"

The selectedTreeIssue expression may contain an Issue context-item that is passed to the template generation by a user selection.

If no issue is selected upon export, the selectedTreeIssue evaluation results in an empty text.

Expression "selectedTreePage" Data center only

The selectedTreePage expression will contain a Page context-item that is passed to the template generation by a user selection.

If no page is selected upon export or page information cannot be retrieved due to application link errors, the selectedTreePage evaluation results in an empty text. There are a few limitations with using this expression – see Restrictions.

Expression "selectedItem" DATA CENTER V4.17 CLOUD

The selectedItem expression will contain an Item context-item that is passed to the template generation by a user selection.

If no item is selected upon export, the selectedItem evaluation results in an empty text.

Expression "server" Data center only

The server expression will be evaluated to result in a Server context-item for further use in expressions.

Expression "users" Data center only

The users expression will be evaluated to result in a Users context-item for further use in expressions.

Expression "variable"

The variable expression can be used to retrieve the value of a variable created by the variable statement.
To access the value of the variable the expression requires the corresponding variable name.
The expression will then be evaluated to the context-item stored in the variable.

Available Expressions