/
User Support Questions

User Support Questions

On this page we document the most asked user support questions. If you do not find an answer to your support question 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.

issue-json-children.PNG

Helper format

{{{jChild "<columns>" "<columns width (optional)" "<filter issue type(optional)"}}}

Examples

{{{jChild "key, summary, assignee, duedate, status" "15,40,15,15,15"}}}
jChild-export.PNG
{{{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

 

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.

 

4. Export {{ and }} characters

 

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

Examples

 

All issue fields including custom fields can be added as table columns

 

6 . Export issue progress

 

7. Export child and sub-task progress

Child and sub-tasks progress are supported with the dedicated helper jProgressChild as a column in the jChild table.

Helper format

 

8. Formatting date field returns invalid date

Some comments date fields are stored in a incorrect date field format. This typically happens for comments created 1-2 days ago. So formatting with the helper {{moment}} returns “invalid date“. The workaround is to use the helper {{jDate}} that returns the actual text string if formatting fails.

 

Related content

How to Export in Word
How to Export in Word
More like this
Reports
More like this
Jira JQL Risk Search
Jira JQL Risk Search
More like this
Templates in Jira
More like this
Export from monday.com
Export from monday.com
More like this
How to Export in Jira
How to Export in Jira
More like this