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 08:01 |
$context.currentUsername | Username of user retrieved when template is being evaluated | |
$context.currentUserId | Atlassian ID of the current user | |
$context.currentUserDisplayName | User full name - retrieved when template is evaluated | John Doe |
$context.currentUserEmail | User's email address - retrieved when template is evaluated | jdoe@mycompany.com |
$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.currentRecipientUser | An object that contains the following properties: displayName, emailAddress, accountId. Can be used to customise outgoing email message to contain details about user who is receiving the notification | Hello $context.currentRecipientUser.displayName |
