Issue and current User Velocity variables

Where is that useful ?

The velocity language can be used to set an advanced field mapping. It allows the user to build a deeper and more custom configuration of an Elements copy & sync operation.

This page gives the whole list of velocity variables that can be used.

Velocity functionnalities

#if (condition) ... #elseif (condition) ... #else ... #end

Builds conditions

#set ($var = "whatever")
Sets an auxiliary variable

Velocity variables

Raw values

$exocetResolver.getValue($issue, "customfield_XXXXX")


$exocetResolver.getValue($issue, "customfield_name")

Retrieves a string representation of the custom field's content.

XXXXX is the id of the custom field


If the custom field value is an issue (ie: Epic link), the Elements Copy & Sync resolver will return the issue.

If the custom field has not value or does not exist, the resolver will return an empty string

If the custom field is an Elements Connect field, the resolver will return the JSON (or XML for Elements Connect v5) stored in database. Use this syntax for Elements Connect field to Elements Connect field mapping.

$exocetResolver.getValue($issue, "customfield_XXXXX.display")


$exocetResolver.getValue($issue, "customfield_name.display")
Retrieves the display content of an Elements Connect field as a string. Use this suffix in a JIRA field mapping when the target field is not an Elements Connect field.
Retrieves the issue id
Retrieves the issue key
Retrieves the issue summary
Retrieves the issue description
Retrieves issue environment
Retrieves the original estimate (in seconds)
Retrieves the estimated remaining time (in seconds)
Retrieves the time spent on issue (in seconds)

Retrieves a JSON table of the component list:

 Click here to expand...
	ProjectComponentImpl {
	ProjectComponentImpl {

Retrieves a table of the affected versions:

 Click here to expand...
[version_name1,version_name2, ...]
Retrieves a table of the fix versions:
 Click here to expand...
[version_name1,version_name2, ...]
The user currently logged in. Its type is the same as $issue.reporter or any other issue actor.
Retrieves $yourDate formatted like "dd/MM/yyyy".
Retrieves $yourDate formatted like "dd MMM yyyy hh:mm".

Named values

$ // $
Retrieves issue type name or id
$ // $
Retrieves issue priotrity name or id
$ // $
Retrieves issue resolution name or id
$ // $
Retrieves issue status name or id

User values

$ // $
Retrieves issue reporter name or id
$ // $
Retrieves issue assignee name or id
$ // $ // 
Retrieves current user name, id or emailAddress

Date values

The following variables return a string formatted as the following example: 2016-07-13 11:45:13.376.

Retrieves the issue creation date
Retrieves the issue updated date
Retrieves the issue due date
Retrieves the issue resolution date
$dateResolver.addDays($yourDate, "X")


$dateResolver.addDays($yourDate, "-X")
Retrieves a date with additional X days ("-" to remove days)
$dateResolver.addMonths($yourDate, "X")


$dateResolver.addMonths($yourDate, "-X")
Retrieves a date with additional X months ("-" to remove months)
$dateResolver.addYears($yourDate, "X")


$dateResolver.addYears($yourDate, "-X")
Retrieves a date with additional X years ("-" to remove years)
$dateResolver.addHours($yourDate, "X")


$dateResolver.addHours($yourDate, "-X")
Retrieves a date with additional X hours ("-" to remove hours)
$dateResolver.addMinutes($yourDate, "X")


$dateResolver.addMinutes($yourDate, "-X")
Retrieves a date with additional X minutes ("-" to remove minutes)
$dateResolver.addSeconds($yourDate, "X")


$dateResolver.addSeconds($yourDate, "-X")
Retrieves a date with additional X seconds ("-" to remove seconds)

Project values

Retrieves the project key
Retrieves the project name
Retrieves the project id
Retrieves the project lead