Each of your JIRA issue fields is assigned to a specific style name, which is used during the export operation

If you do not see a field you would like to export, please let us know at support@softwareplant.com!

When you open an exported Jira issue document, using a document editor such as MS Word or Open Office Writer, you will notice that new styles are available and you can modify them.

A style is a set of formatting characteristics, such as font name, size, color, paragraph alignment and spacing. Some styles even include borders and shading.

Using styles to format your document, you can quickly and easily apply a set of formatting choices consistently throughout your document.

For example, instead of taking three separate steps to format your heading as 16-point, bold, Cambria, you can achieve the same result in one step by applying the built-in Heading 1 style. You do not need to remember the characteristics of the Heading 1 style. For each heading in your document, you just click in the heading. Here's more info about styles for the curious: clickety click!

Remember that you can upload your own files as templates. This means that you can download one of the supplied ones, customize it using styles and upload again to have your own template!

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

In version 2.0 the prefix was changed from SP (like SoftwarePlant) to BT (like BigTemplate).

 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:

JIRA fieldStyle name
AssigneeBT.task.assignee
StatusBT.task.status
fixVersionBT.task.fixVersion
KeyBT.task.key
LabelsBT.task.labels
PriorityBT.task.priority
SummaryBT.task.summary
ProjectBT.task.project

You can find the full list of all styles with examples in this sample document: 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.