Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

You must have the Jira Cloud System Administrators global permission before you can carry out the instructions on this page.

Overview

The E-Mail Templates Administration screen let you able to add, edit, delete and review your templates configurations.

The Approval Request tab let you able to setup the templates to apply for the e-mails notifying an approval request.

The Approval Reply tab let you able to setup the templates to apply for the e-mails notifying an approval reply.

Default Approval Request and Approval Reply Templates

When installing the app, if no customization is applied, the Approval Request and the Approval Reply emails follow the Default Templates.

Default Approval Request e-mail template

Default Approval Reply e-mail template

You are able to customize the Default Templates and furthermore, you can undo the customization by clicking Reset Default Template.

Operations

The E-mail Templates administration screen allows you to perform the following operations on an already existing E-Mail template:

  • Edit template configuration, open the Email Template Configuration screen allowing to setup the information appearing on the email

  • Copy template, create a new template from a copy of the selected one

Copy template

When copying an Email Template, a new template is created that has the same configuration of the copied template but not its Project or Conditional Rule association. 

Edit template main settings

The available operations on Approval Request and Reply  E-Mail templates include the capability to update the Project or the Conditional rule that are evaluated to use the Custom Approval Request and Reply E-Mail templates instead to the Default templates.

Delete template

When deleting an Email Template the data on existing Mappings and existing issues are made consistent.

Custom E-Mail Templates

The Email Template Configuration screen allows you to setup the information appearing on the email.

This sections illustrate the available optional settings and how to setup them.

Optional settings common to all templates

Header

Subject

Issue Type

This setting allows you to enable displaying the issue type in the email body.

Assignee

This setting allows you to enable displaying the issue assignee in the email body.

Issue Creation Date

This setting allows you to enable displaying the issue creation date in the email body.

Project

This setting allows you to enable displaying the issue Project in the email body.

Priority

This setting allows you to enable displaying the issue Priority in the email body.

Reporter

This setting allows you to enable displaying the issue Reporter in the email body

Workflow Transition

This setting allows you to enable displaying the Workflow transition on approbation in the email body.

Approval buttons

You have the capability to enable Approval buttons showing on the email in order to allow the approver to reply by clicking them.

When you enable Approval Buttons you are able to manage the following options by clicking on the Configuration Icon:

  • Button Placement

  • Comment screen popped up

  • Button Links

Button Placement

You can choose  if the Approval Buttons appear on the Bottom (Default) or on the Top of the email body.

Comment screen popped up

You can choose  if by clicking an approval button the action is processed immediately or the screen requiring the Approval Comment appears only if the Approval Comment is mandatory or in any case.

You can choose where do you want that buttons links redirect the user.

Available options are:

  • Approval page (Default), the user displays a built-in Approval form that allows to insert a comment and credentials (when enabled)

  • Jira ticket, the user is redirected on the concerned Issue view screen in Jira

You are able to insert a text that will display on the email footer.

The email will render the Html tags.

  • No labels