Skip to main content

Project-scoped templates

Every custom template has one of two scopes:

  • Company-wide — available in every Jira project.
  • Specific project — available in exactly one Jira project.

Project scoping is included in both Free and Standard. It is not an add-on and does not require an edition upgrade.

Why scope templates​

  • Keep each project's export pickers focused and uncluttered.
  • Let teams own their own document designs.
  • Reduce the risk of using the wrong template.

Set or change the scope​

Choose the scope in the template editor when you save. The template list shows a scope badge so administrators can immediately see where each template is available.

Project administrators can create and edit templates for their own project. Site administrators can also manage company-wide templates, move a template between projects, and change a project template to or from company-wide scope.

Diagram of template visibility: company-wide versus project-scoped templates Company-wide templates are available everywhere; a project template belongs to exactly one project.

Visibility and export safety​

An export picker shows company-wide templates plus templates for its current project. A project template never appears in another project's picker. The same rule is enforced on the server, so supplying a hidden template ID directly does not bypass the scope.

For JQL, board, sprint, release and backlog exports, every exported issue must belong to the template's project. A mixed-project or empty result cannot use a project template. Use a company-wide template for multi-project exports.

Scheduled exports​

Exportelier Automation shows the scope next to each template. A schedule can use a project template only when every issue returned by its issue or JQL source is in that project. The source is checked when the schedule is created, changed or re-enabled, and again on every run.

Free template limit​

Free includes three custom templates per Jira site, regardless of scope. A mix such as two company-wide templates and one project template uses all three slots. The limit is not reset per project. Standard allows unlimited custom templates, subject to fair use.

Existing templates without an explicit scope remain company-wide. See Managing templates.