Skip to main content

Managing templates

Templates are managed by administrators. This page covers the lifecycle of a template.

Creating and duplicating​

Create a template from scratch or duplicate an existing one. Duplicating a bundled default is the fastest way to start, because the structure is already in place.

Template management screen The template list with create, duplicate, rename and delete actions.

Naming​

Use clear, purpose-based names (for example, "Customer release notes" or "Audit issue export") so the right template is easy to pick at export time.

Who can edit​

Template management is admin-only. Regular users select from available templates when exporting but cannot change them. See Permissions & roles.

Project-scoped templates​

When saving, choose Company-wide or Specific project. Company-wide templates appear in every project; a project template appears only in its one assigned project. Scope badges in the template list make the distinction visible. Project scoping is available in both Free and Standard — see Project-scoped templates.

Dashboard Report Standard​

Dashboard Report Standard is a bundled report template for Search, Board, Sprint, Release, and Backlog exports. It summarizes the current exported issue set with three Category charts: Status as a Pie, Issue type as a Donut, and Priority as horizontal bars.

Open it directly to preview the report. To customize it, duplicate the template and edit the copy; the bundled original remains a restorable baseline. Restoring defaults adds Dashboard Report Standard exactly once and does not change your context defaults.

Despite the name, this template does not read anything from Jira dashboards — it summarizes whatever issue set you are exporting. To build a report from an actual Jira dashboard, see dashboard import.

Deleting​

Deleting a template removes it from the export pickers. Because version snapshots and bundled defaults exist, you can recreate or restore a baseline if needed.