Advanced customization

The list of styles can be presented in a separate pane (Styles task pane can be opened with the keyboard shortcut Alt+Ctrl+Shift+S).

The styles listed in the pane start with a prefix "BT.task." The first word always starts with a lowercase and the following ones depending on how they were named in Jira, there's no spaces between words.

You can add a space after the name of a style to add additional description to help you identify the desired style:

• BT.task.summary header
  
• BT.task.summary footer

 Supported field types

Jira standard fields

The style name should include the Jira field as explained above. For standard JIRA fields, it's rather simple:

You can find the list of available styles with examples in on this page: Click!

E-mails

Assignee and reporter e-mail support are supported. To make them appear in a document, use the identifiers:

BT.task.assignee#email

BT.task.reporter#email

QR codes

Image identifier BT.task.key#qr generates QR code with a link to the issue.

Custom field types

• Number
• Select List (multiple choice)
• Select List (single choice)
• User Picker
• Date Picker
• Labels
• Text Field (multi-line)
• Text Field (single line)

For custom fields, you need to find out how a given field is named in your JIRA instance - the field ID is used for this. To do so, go to JIRA Administration->Issues→Custom Fields:

To obtain the ID, you need to right-click a custom field on your JIRA issue screen and hit Inspect Element - the Id will be clearly shown as a numerical value (10400 as an example below for field 123):

The pattern is BT.task.custom.<ID-here>. e.g. BT.task.custom.customfield_10001
It can be looked up in leave.docx default template -> date from and date to is a custom field.

Fonts

Fonts need to be embedded if a template uses custom ones. This can be done in MS Word in the Options section shown below:

Note: this feature is not available on the Mac version of Office 365.