LogoLogo
๐Ÿ‘‰ Get a free ITSM ebook
Issue Scheduler
Issue Scheduler
  • โžก๏ธAbout Issue Scheduler
  • Examples of templates
  • Comparison table
  • Basic
    • Get started
    • Type of templates
    • Create template
      • Trigger types
      • Cross-project templates
    • Use template to create issue
    • Manage templates
    • Supported custom field types
      • Support for third-party apps
  • Advanced
    • Subtasks templates
    • Variables
    • Relative Due date
    • Permissions
    • Execution history
  • Jira Software
    • Create stories templates
    • Add issue to Sprint
  • SITE ADMINISTRATOR
    • App installation
    • Manage all templates
  • FAQ
  • ๐Ÿ”ฎRoadmap
  • ๐ŸคSupport
    • Book a demo session
    • Raise a request or bug
    • Appsvio website
  • ๐Ÿ”Security statement
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com ยฉ 2025 All rights reserved

On this page
  • Public templates
  • Private templates
  • Cross-project templates
  • Template type selection
  • Examples of two types of templates

Was this helpful?

Export as PDF
  1. Basic

Type of templates

The differences between the template types

You can create three types of templates: Public, Private, and Cross-project.

Public templates

Theyโ€™re available for every user in your Jira instance. When you create them, youโ€™re an owner of these templates, so only you can modify or delete them. Other users can execute these templates manually to create issues. They can also duplicate them to use to create their own templates.

This is a default configuration. You can modify it during template creation and define which users see these templates and can modify them. Itโ€™s especially useful for large organizations.

Private templates

As the name suggests, such templates are hidden from others. Theyโ€™re private. You, as the owner of this template, are the only one who can do anything with them.

Cross-project templates

In the case of private and public templates, when creating them, you define in which projects the issues from the given template will be created. In case of cross-project templates, you define a generic template using the basic fields in Jira, and only when you use it, you choose in which project you want to create the issue.

Unlike the other templates, cross-project template can only be executed manually. The rest can be scheduled and executed automatically. We recommend using this type of template when the template will be used in many different projects, even those that haven't been created yet.

Read the table below for detailed information.

Actions

Owner

User (not-owner)

Jira administrator

Private template

Update template

โœ…

โŒ

โœ…

Run template manually

โœ…

โŒ

โœ…

Set ON/OFF

โœ…

โŒ

โœ…

Duplicate template

โœ…

โŒ

โœ…

Remove template

โœ…

โŒ

โœ…

Public template

Update template

โœ…

โŒ (but it can be changed in the configuration)

โœ…

Run template manually

โœ…

โœ…

โœ…

Set ON/OFF

โœ…

โŒ (but it can be changed in the configuration)

โœ…

Duplicate template

โœ…

โœ…

โœ…

Remove template

โœ…

โŒ (but it can be changed in the configuration)

โœ…

Template type selection

You can select template type during template creation or update. This change will not impact the template execution calendar.

Once you choose cross-project, you won't be able to change it later. Private and public templates can be changed among themselves.

Examples of two types of templates

PreviousGet startedNextCreate template

Last updated 1 year ago

Was this helpful?

Jira administrator can manage all templates which are on the current Jira instance. Read more .

A list of examples you can find under the page.

on this page
Examples of templates