Page History

...

If you are exporting a date field such as CreatedDate and LastUpdateDate, you can define the format of how the date is displayed. All the patterns supported by the SimpleDateFormat Java API are supported.

Definition:

${dateformat("<Format>"):<Field name>}

Code Block

title	Expand to see the examples on sample code
collapse	true

${dateformat("yyyy-MM-dd"):Created}
${dateformat("EEE, MMM d, ''yy"):Created}
${dateformat("EEE, d MMM yyyy HH:mm:ss Z"):Updated}

Formatting Number Field

Info
Available :in Xporter for Jira 3.3.0 and later.

If you are exporting a Number Field, you can define the format of how the number is displayed. All the patterns supported by the DecimalFormat(String pattern) Java API are supported.

You can also specify the Locale you want to use. All the Locales in JRE 7 Supported Locales page are supported.

Definition:

${numberformat( "<pattern>" ):<Field name>}

${numberformat( "<Locale>" , "<pattern>" ):<Field name>}

Code Block

title	Expand to see the examples on sample code (considering Price as a custom Number Field)
collapse	true

${numberformat("###,###.###"):Price}
${numberformat("\u20AC ###,###.###"):Price}
${numberformat("de_DE" , "###,###.###"):Price}
${numberformat("##0.#####E0"):Price}
${numberformat("en_UK" , "#0.#####%"):Price}

...

Info
In Xporter for Jira 4 and later, displayname and displayemail function were replaced by new functions: fullname and emailaddress, respectively.

If you are exporting a User Picker or Multiple Users custom field, you can output the Display Name using the fullname functionthe fullname function.

Definition:

${fullname:<Field name>}

Code Block

title	Expand to see the example on sample code
collapse	true

${fullname:UserCustomField}

...

If you are exporting a User Picker or Multiple Users custom field, you can output the email using the emailaddress function.

Definition:

${emailaddress:<Field name>}

Code Block

title	Expand to see the example on sample code
collapse	true

${emailaddress:UserCustomField}

Escaping fields

If the fields to be exported need to be escaped there is a function for that. Escaping This function allows fields with line breaks or other special characters to be used inside JavascriptJavaScript.

Definition:

${escape:<Field name>}

Code Block

title	Expand to see the examples on sample code
collapse	true

${escape:Description}
${escape:Custom Field}
 
%{('${escape:Description}'.length > 0) ? 'This issue has description': 'This issue does not have description'

Creating mappings based on

...

JavaScript using formatted fields

There are times when it may be needed to format a field, execute javascript JavaScript actions on the formatted field, and export the result as HTML or WIKIWiKi.
In this these cases, all the above formatters are available.

Code Block

title	Expand to see the example on sample code
collapse	true

${html:%{'${escape:Description}'.replace(new RegExp('toReplace','g'),'replacer')}}

...

If you are exporting a duration time field, you can define the behavior you want in order to get the correspondent value. Let's suppose you want to export the duration of an issue, from now on, you are able to you can get this value in milliseconds and even better, you can get the current duration time formatted as well as the formatted version of this value.

Furthermore, this field allows you to execute javascript JavaScript action on the duration time field and export the result.

Definition:

${durationformat:<Field name>}

Code Block

title	Expand to see the example on sample code
collapse	true

${durationformat:Custom Field}

${durationformat:%{var timeValue="<Value>"; timeValue;}}

Page tree

Versions Compared

Old Version 30

New Version 31

Key

Formatting Number Field

Escaping fields

Creating mappings based on

JavaScript using formatted fields