DATA CENTER AND SERVER | CLOUD

Word Export FAQ

Owned by Support Advocate (ease solutions)
Last updated: Apr 26, 2024 by Bernhard Doleschel
Contents

Exporting Jira rendered content with the wiki statement

 View details...

To retain JIRA rendered content (e.g. description format on JIRA), the wiki statement can be used.

Example JIRA description:

The following template contains two context items for description. One using plain text output and the other using the wiki statement which will output rendered content. 

 

  • Any formatting done on the template will not be rendered if the wiki statement is used.
  • Pictures in the JIRA description will not be downloaded if the wiki statement is not used.

Export Template Configuration not displayed

 View details...

To activate the option:

  1. Click Administration
  2. Select Add-ons
     
  3. On the Requirements for JIRA section, select Permissions
  4. Configure on the following page the access to the export template configuration.
    • "Restrict User Access" to NO will allow anyone to use the export template configuration
    • "Restrict User Access" to YES will allow you to configure who would be able to use the export template configuration

Adding export information to the export template

 View details...

The following examples will include the user information in the export template

Include the information of the issue reporter:


Screenshot


 Template
[[\each $selectedTreeIssue]]
[[$.reporter.displayname]]
[[/each]]

Export result 
John Doe

If no issue is selected on the project tree during export, the name will not be displayed on the export result

Get the display name of all users


Template
[[\each $users]]
[[$.displayname]]
[[/each]]

Export result 
John Doe Molive   
Gail Forcewind
Paige Turner

Getting familiar with the "selected" expressions

 View details...

The selected expressions refers to the current items on the Requirements tree.

selectedProject and selectedFilter

Screenshot:

selectedFilter

Template

[[\filter $selectedFilter]]
  Issue key: [[$.key]]
[[/filter]]

Result

Issue key: SC-6
Issue key: SC-5
Issue key: SC-4
Issue key: SC-3
Issue key: SC-2
Issue key: SC-1
selectedProject

Template

[[\template issue-display]]
  Issue Key : [[$.key]]
[[/template]]
 
[[\jql project = $selectedProject order by key desc]]
  [[\apply-template issue-display]] [[/apply-template]]
[[/jql]]

Result

Issue key: SC-6
Issue key: SC-5
Issue key: SC-4
Issue key: SC-3
Issue key: SC-2
Issue key: SC-1

selectedTreeFolder

Screenshot:

selectedTreeFolder

Template

[[$selectedTreeFolder]]

Result

GUI Specs

selectedTreeIssues

Screenshot:

selectedTreeIssue

Template

[[$selectedTreeIssue]]

Result

SC-6

Exporting issue custom fields

 View details...

The Issue context item supports the rendering of custom field values during export.

This can be achieved by using the custom field name as context placeholder in the Issue iteration.

Example usage for a custom field with name "Acceptance Criteria".

    [[$."Acceptance Criteria"]]


The result rendered shall be the custom field value.

For values that require special format rendering, please use the wiki statement with this context item.

Known issues