Export & Import

Templating.app now allows you to export and import Issue Templates, making it easy to transfer templates between projects, back them up, or share them with your team. Instead of manually recreating templates, you can now save them as JSON files and import them whenever needed.

Danger

Importing a template will replace all existing data in the current template. This action cannot be undone, so be sure before proceeding.

Export an Issue Template

Exporting an Issue Template allows you to download its configuration as a JSON file.

Steps to Export

1. Open the Issue Template you want to export.
2. Click on Details in the top right corner.
3. Click on the three-dot icon (•••).
4. Select Export. Your template will be downloaded as a JSON file.

Tip

Keep exported files as template backups or to share templates with teammates.

Import an Issue Template

Importing an Issue Template allows you to restore a previously exported template or move it to another project.

Steps to Import

1. Open an existing Issue Template or create a new one.
2. Click on Details in the top right corner.
3. Click on the three-dot icon (•••).
4. Select Import.
5. Choose the JSON file you previously exported. Follow the on-screen instructions to complete the import process.

Known issue: templates with permissions

If the template you exported has permission restrictions configured, the import currently stops at the Details step and reports that not all parts of the file could be imported. As a workaround, open the exported JSON file in a text editor, delete the "restrictions" block inside the "template" object near the top of the file, and import again. Nothing else needs to change. We are working on a fix.

Danger

Importing a template will completely replace all existing data in the selected template. There is no undo option.

What an export contains

An export is a backup of the template, not of the work items created from it. It covers the template details, the issue hierarchy and the form variables.

Two things are not carried over by an import:

• Permissions. If the original template has permission restrictions configured, they are not applied to the imported template. Set them again after importing.
• Instance specific values. Issue type IDs, custom field IDs, components, versions, groups and users belong to the site and project they came from. Importing into a different site or project does not remap them, so review those fields afterwards.

For moving templates between projects or sites, see Migrate templates and issues.

Limits

Work items per template	500
Child items per work item	500
Hierarchy depth	no limit
Issue Templates per project	60
Form variables per template	20
Options per select variable	20
Custom fields per work item	50