Besides fields from $issue object you can also refer several other variables from $context. They are convenience variables and are available in every notification by default
This table shows what you can get from $context
Variable | Meaning | Example |
|---|---|---|
$context.today | Current day - evaluated when template is executed | 2016-10-15 |
$context.yesterday | Yesterday - evaluated when template is executed | 2016-10-14 |
$context.sevendaysago | 7 days ago - evaluated when template is executed | 2016-10-07 |
$context.timezone | Timezone as defined in your JIRA instance | UTC |
$context.onehourago | beginning of previous hour in format yyyy-MM-dd'T'HH:mm:ss.SSSZ | 2016-10-15T22:17:31.661+0200 |
| $context.last_run | Date when the scheduled messaging was last run. Applicable to digested notifications only | 2016-10-07 |
$context.currentUsername | Username of the user who triggered the Jira event | |
$context.currentUserDisplayName | Full name of the Jira user who triggered event | John Doe |
$context.currentUserEmail | Email address of Jira user who triggered tevent | |
$context.destination | Destination of message. Email, slack channel or HipChat room | #general |
| $context.baseurl | Base URL of JIRA installation. Useful for rendering links to issues | https://jiraserver.mycompany.com:2990/jira |
| $context.customFieldManager | Access to com.atlassian.jira.issue.CustomFieldManager | |
| $context.issueManager | Access to com.atlassian.jira.issue.IssueManager | |
| $context.diffUtils | Access to com.atlassian.jira.mail.DiffUtils | |
| $context.textUtils | Access to com.opensymphony.util.TextUtils | |
| $context.jiraVelocityHelper | Access to com.atlassian.jira.util.JiraVelocityHelper | |
| $context.i18n | Access to com.atlassian.jira.util.I18nHelper | |
| $context.currentRecipientUser | Access to ApplicationUser object that contains data about the Jira user who will receive the current notification Note, that your notification configuration should be sending as Multiple Emails |
