On this page we document the most asked user support questions. If you do not find an answer to your support request please file a ticket here.
1. Export child issues and sub-task in customizable table
All child and sub-task issues are found in the issue JSON child property (see below picture from editor view data tab). To make it easy to export child issues in table we have developed a dedicated jChild helper.
Helper format
{{{jChild "<columns>" "<columns width (optional)" "<filter issue type(optional)"}}}
Examples
{{{jChild "key, summary, assignee, duedate, status" "15,40,15,15,15"}}}
{{{jLinked "link, key, summary, duedate, status" "15,15,40,15,15" "Bug"}}}
All issue fields including custom fields can be added as table columns
2. Export individual child and sub-task fields
All child and sub-task issues are found in the issue JSON child property (see below picture from editor view data tab).
Examples
{{#each children}} //simple text, number custom field {{fields.customfield_10014}} //description {{{jHtml renderedFields.description}}} //user picker custom field {{fields.customfield_10041.displayName}} //date custom field {{jDate fields.customfield_10033 "YYYY-MM-DD"}} //multiselect custom field {{jArray fields.customfield_10039 "value"}} //html custom field {{{jHtml renderedFields.customfield_10031}}} //truncate number value {{toFixed fields.customfield_10035 1}} //filter on specific status {{#ifeq fields.status.name "In Progress"}} this child has status In-Progress {{/ifeq}} {{/each}}
3. Export sub-tasks in a table (manual advanced)
The challenge is to keep the table first row static and then add the sub-tasks row below. To achieve this you need you need to add the sub-task iterator <!--{{#each fields.subtasks}}--> <!--{{/each}}--> as a HTML comments in the editor HTML view. See below screenshots of an example table and the corresponding editor HTML.
<!DOCTYPE html> <html> <head> <meta format="a4" orientation="portrait" sortfield="" sortorder="asc"> <title></title> </head> <body aria-disabled="false"> <br> <table style="width: 100%;"> <tbody> <tr> <td style="width: 25%; background-color: rgb(97, 189, 109);">Key</td> <td style="width: 25%; background-color: rgb(97, 189, 109);">Summary</td> <td style="width: 25%; background-color: rgb(97, 189, 109);">Status</td> <td style="width: 25%; background-color: rgb(97, 189, 109);">Project</td> </tr> <!--{{#each fields.subtasks}}--> <tr> <td style="width: 25.0000%;">{{key}}</td> <td style="width: 25.0000%;">{{{jExtend key "fields.summary"}}}</td> <td style="width: 25.0000%;">{{{jExtend key "fields.status.name"}}}</td> <td style="width: 25.0000%;">{{{jExtend key "fields.project.name"}}}</td> </tr> <!--{{/each}}--> </tbody> </table> <br> <br> </body> </html>
4. Export {{ and }} characters
{{{{raw}}}} {{escaped}} {{{{/raw}}}}
5. Export linked issues in customizable table
You can export linked Jira issues in a number of different ways. Below table handlebar helper allows you to export any fields including custom fields, set column width and finally filter on both link type and issue status.
Helper format
{{{jLinked "<columns>" "<columns width (optional)" "<filter on link type and issue status (optional)"}}}
Examples
{{{jLinked "link, key, summary, assignee, duedate, status"}}}
{{{jLinked "link, key, summary, duedate, status" "15,15,40,15,15" "blocks,story"}}}
All issue fields including custom fields can be added as table columns
6 . Export issue progress
{{{jProgress}}}
7. Export child and sub-tasks progress
Child and sub-tasks progress are supported with the dedicated helper jProgressChild as a column in the jChild table.
Helper format
{{{jChild "key, summary, jProgressChild, status" "15,40,30,15"}}}