Page tree
Skip to end of metadata
Go to start of metadata

SLA Notifiers can be configured to notify relevant people before or after the breach. Notifier can be chosen to work with SLAs' working calendar. It also can be enabled to work as a recurring notifier.


About enabling working calendar

When the working calendar is checked notification will only be sent in the working hours of the related calendar.

About recurring notifier

If recurring notifier is enabled, TTS will keep relevant people notified within every given recurring interval until the completion of SLA. For instance, if recurring interval is defined as 30m and notify before is defined as 2h, then TTS will send first email 2 hours before the deadline, and it will send emails every 30 minutes till SLA becomes completed.

Email subject and body can be fully dynamic.
Parameters that can be passed to SLA Notifier  are listed below

${slaDescription}StringName of the SLA
${slaValue}StringSLA value as a time string
${slaStartDate}StringStart time of the SLA
${slaEndDate}StringEnd time of the SLA
${slaNotifyBefore}StringNotify before parameter in notification settings
${originStatus}StringOrigin status name, null if origin is not set by status
${targetStatus}StringTarget status name, null if target is not set by status

Indicates whether or not SLA is exceeded (v7.1.0+)

#if(${slaExceeded})You missed SLA deadline#end
${slaRemainingTime}StringRemaining duration of SLA (e.g. 1h 30m) (v7.1.0+)
${slaOverdue}StringOverdue duration of SLA (e.g. 1d 10h) (v7.1.0+)
${issue}IssueIssue object to retrieve various issue attributes (e.g. ${issue.summary} )

CustomFieldManager could be used to insert custom field values into email text


DateTool could be used to format dates. (v7.7.0+)

$dateTool.format('d-M-yyyy H:m:s', ${issue.getCustomFieldValue($customFieldManager.getCustomFieldObject('customfield_11201'))})

DateTimeFormatter could be used to format dates with pre-defined formats in JIRA. (v7.7.0+)





Handy tip for template variables

 Many times custom fields or other fields on the issue might have a null value resulting in variable names displayed in e-mail content. To prevent this simply put an ! after $ sign on variable name like this:


In the following part, recipients (assignee, reporter, project roles or even email addresses) can be configured. 


There is a 'Preview' button to test the email template, type sample issue key and press the button.

  • No labels