Issue Templates

Issue Templates for Jira Cloud ensures data privacy and security by not retaining any user-specific information from the client’s Jira instance, except for instance description and identification data required for authentication during installation. The app uses SSL protocol to encrypt data transmission between the Jira instance and its server. This includes templates, issues, project configuration, and user-executing templating process information. Rest assured that the app follows standard procedures for data protection as per Atlassian’s guidelines.

1. Selecting a template on a screen: Simply choose a template from the dropdown menu directly on the screen, and all fields will be automatically populated based on the Set of Fields settings.

2. Setting up a default template for a project: Select a template as the Default for a specific project and issue type pair. This will automatically apply the template to every new issue created in that project.

3. Applying a template to an existing issue: If you need to apply a template to an already existing issue, use the “Apply template” option found under the “More” menu on the issue view. A dialog will appear, displaying all fields currently added to the edit issue screen in the project.

4. Advanced automation during workflow transitions: Utilize the Deviniti [Issue Templates] – Create structure post function and configure it to select a template. This will automatically apply the template to every issue that goes through the selected workflow transition, including the ability to copy sub-tasks or issue links.

Issue Templates for Jira Cloud supports Service Management projects but may have limited compatibility with the Customer Portal. To enable templates on the portal, ensure the “Allow Customers to use templates via customer portal” option is enabled in global configuration.

To disable Issue Templates notifications, follow these steps:

1. Go to the Issue Templates menu in the Jira top bar and select Configuration.
2. In the General tab, click on the pen icon next to the “Enable notification panel” option.
3. Uncheck the checkbox to disable notifications.
4. Save the changes.

To hide the Issue Templates menu:

1. Go to the Issue Templates global configuration as a Jira administrator
2. Access the UI Visibility tab
3. Check the “Hide the top navigation item” checkbox and save the changes.

To resolve this, ensure that the Jira Service Management application is enabled and has a valid license. Once confirmed, re-enable the Issue Templates app by navigating to Jira administration → Manage apps. Rest assured that re-enabling the app will not result in any configuration loss, as all settings are stored in your Jira database.

In Jira Data Center, the Templates Repository project allows you to manage and configure Issue Templates. However, certain restrictions can be applied to control template creation and configuration using Permissions settings. For instance, you have the option to modify the “Create Issues” permission to restrict template creation.

If essential permissions such as Administer Projects, Browse Projects, Create Issues, Close Issues, or Edit Issues are missing in the Templates Repository project, a warning message may appear in the global configuration.

To resolve this, you can navigate to the Templates Repository Project settings, specifically to the Permissions section, and grant the missing permissions as needed.

1. The template is disabled: Ensure that the template is in the “Published” status. Draft templates are not ready for use until they are published. You can enable a template in the Issue Templates Details panel by navigating to Availability → Create Issue Screen.
2. The template lacks a descriptive name: Newly created templates are assigned the name “Default Template Name.” Change the template’s name to something descriptive for easy identification in the list of available templates. Modify the name in the General tab of the Issue Templates Details panel.
3. Excluding context set in the Availability tab: Check the Availability tab settings for projects, issue types, screens, and other factors where the template should be available. Ensure there are no exclusions preventing the template from being applied where desired.

Issue Templates Cloud acts like regular Jira issues, but sometimes fields from templates may not copy to newly created issues. To address this, access the Scopes settings under Templates Repository project settings or Template configuration panel to determine the fields that should be copied.

If the “Create from template” link is missing, it might be due to restricted visibility for specific user groups. To resolve, go to Jira settings → Apps → Issue Templates configuration, open the UI visibility tab, and adjust the groups selection for displaying the link.

To resolve this, remove the “Epic Link” field from the set of fields assigned to the story templates.

Issue Templates for Jira offers two sets of fields for post-function, each serving specific purposes:

Main set of fields:

• Automatically fills values on the create/edit/transition issue screen.
• Filling field values directly from the selected template in the “Template” dropdown.
• Supports Jira system fields and custom fields.

Different Set of Fields:

• Provides background filling for more complex structures. Enables copying of values from the template, even if they are not displayed during issue creation.
• Supports Jira system and custom fields, including Attachments and Issue Links.
• Fills fields during a workflow transition.