---
title: "Exercise 1 - Printing Issue Data"
canonical: "https://docs.getxporter.app/space/XPORTERCLOUD/528378/Exercise%201%20-%20Printing%20Issue%20Data"
format: markdown
---
> Macro (rw-ui-expands-macro)
> 
> > Macro (rw-expand)
> 
> > Macro (toc)

# Introduction

The primary objective of this initial exercise is to provide you with an understanding of how [Xporter for Jira Cloud](https://marketplace.atlassian.com/apps/891368/xporter-export-issues-from-jira?tab=overview&hosting=cloud) functions in printing issue data onto a [Template](https://docs.getxporter.app/space/XPORTERCLOUD/427622) or document.

As explained [here](https://docs.getxporter.app/space/XPORTERCLOUD/558575/Mappings), printing Issue data onto a document is based on [mappings](https://docs.getxporter.app/space/XPORTERCLOUD/558575) with the following notation: `${<Issue Field>}`

> ℹ️ This notation is applicable to both native and custom fields, requiring only the definition of the field name.

During document processing, Xporter retrieves all necessary data from the specified Jira Issue and inserts it into the Template. The result is your Template filled with the data from the Issue.

In this exercise, you will learn how to print issue data onto a Template.

# Printing Issue Data

> Macro (rw-ui-steps-macro)
> 
> > Macro (rw-step)
> 
> Create a new Word document to begin defining which fields will be printed.
> 
> > Macro (rw-step)
> 
> <span style="color: #0d0d0d">Use the fields listed in the table below.</span>
> 
> | **Fields** | **Description** |
> | --- | --- |
> | ProjectName | The issue project name |
> | ProjectKey | The issue project key |
> | Key | The internal issue Key |
> | Summary | The issue Summary |
> | IssueType | The issue type |
> | Priority | The issue priority |
> | Status | The issue status |
> | Description | The issue description |
> | AssigneeId | The issue assignee Jira user account ID |
> | ReporterId | The issue reporter Jira user account ID |
> | Created | The issue creation date and time |
> | Updated | The date and time when the issue was updated |
> 
> > ℹ️ <span style="color: #0d0d0d">Ensure all fields you intend to print are populated in the issue; otherwise, they will appear blank. </span>
> > ℹ️ 
> > ℹ️ <span style="color: #0d0d0d">These fields represent only a small subset of </span>[<span style="color: #0d0d0d">all available fields</span>](https://docs.getxporter.app/space/XPORTERCLOUD/558575/Mappings)<span style="color: #0d0d0d">.</span>
> 
> > Macro (rw-step)
> 
> The fields using the notation *${<Issue Field>}* are as follows:
> 
> ```
>    ${ProjectName}
>    ${ProjectKey}
>    ${ProjectName}
>    ${Key}
>    ${Summary}
>    ${IssueType}
>    ${Priority}
>    ${Status}
>    ${fullname:AssigneeUserName}
>    ${fullname:ReporterUserDisplayName}
>    ${dateformat("dd-MM-yyyy HH:mm:ss"):Created}
>    ${dateformat("dd-MM-yyyy HH:mm:ss"):Updated}
> ```
> 
> > ℹ️ Dates are printed in standard ISO format but can be formatted using the *[dateformat](https://docs.getxporter.app/space/XPORTERCLOUD/558535/Formatting+Fields)*[ function](https://docs.getxporter.app/space/XPORTERCLOUD/558535/Formatting+Fields).
> 
> > Macro (rw-step)
> 
> Xporter allows customization of the template layout, including headings, tables, images, text styling, and more. Refer to the sample below (Figure 1) for an illustration of template mappings displayed in a Microsoft Word template.
> 
> ![Figure 1 - Customized template](media://146bcacd-a4bf-4a6e-b112-b3bda500dc80)
> 
> This template includes:
> 
> - A header with a logo (Figure 1 - 1).
> - Headings (Figure 1 - 2).
> - Text styling (Figure 1 - 3).
> 
> > Macro (rw-step)
> 
> Once your template is complete, [upload it to your Jira instance using the "Templates" menu option](https://docs.getxporter.app/space/XPORTERCLOUD/427622/Working+with+Templates#Adding-an-External-Template) in the Xporter for Jira Cloud administration section. Define where your template will be available by selecting the scopes.
> 
> > Macro (rw-step)
> 
> Finally, navigate to the issue you wish to export, select your template and output format, and click *Export*. Refer to the sample below (Figure 2) for an example of how the generated template will appear after being populated with issue data.
> 
> ![Figure 2 - Template](media://b7651aad-3d10-40f5-a6dd-233c52821fa8)


<details>
<summary>Exercise 1 Resources</summary>

| **File** | **Description** |
| --- | --- |
|  | **Exercise 1 -** Sample template file |
|  | **Exercise 1 -** Sample generated file |
</details>


> ℹ️ **This exercise is now complete. Proceed to **[**Exercise 2**](https://docs.getxporter.app/space/XPORTERCLOUD/430432/Exercise+2+-+How+to+Populate+Rendered+Fields+Using+Wiki+or+HTML+Formatting)** to learn how to** populate rendered fields using Wiki or HTML formatting.
> ℹ️ 
> ℹ️ If you like this exercise, please leave a comment or a 👍. Your feedback is very important to us.
> ℹ️ 
> ℹ️ Thank you in advance. Enjoy our product.


<details>
<summary>Support/Troubleshooting</summary>

If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://docs.getxporter.app/space/XPORTERCLOUD/18251779/In-App+Chat+Support).
</details>