Placeholders | Advanced Details
- Maria Fakas (Deactivated)
You can use these dynamic placeholders to show the actual values that you want the recipient to see. Insert placeholders in the notification subject, message, footer, Slack, or any REST API call. Apply placeholders both in template editor end when creating your own hardcoded email template.
For issue-specific placeholders, this is more interesting if you are using the event trigger configuration.
Placeholders in Template Editor
Add placeholders in Template Editor by using Issue and Non-issue Fields from the Blocks panel. Set up the Field Name in the Settings tab. If you write placeholders in a Text Block, you won't see them highlighted as a field block, but they will be replaced in your email with the corresponding value.
Placeholders in Hardcoded Email
You can create and import a hardcoded email template using both Issue and Non-issue placeholders. In the incoming emails, you will get appropriate values from Jira. Please, note: today, we don't allow users to modify their templates in Notification Assistant Template Editor. To learn more about Importing Templates, read this page.
Placeholders in Slack message
Provide the message you need to deliver to your Slack channel. Include Issue or Non-issue placeholders in the Message section when adding a Slack Channel in Notification Assistant administration. When using a Test Message functionality, you won’t see replaced placeholders. You’ll get substituted values in triggered notifications.
If you are using issue placeholders without the event trigger, it will choose the value from the first issue in the result set.
List of placeholders:
Placeholder | Issue placeholder | Description |
|---|---|---|
${username} | Non-issue field | Gives you the Jira username of the recipient. Note that this will not apply to external recipients! |
${fullname} | Non-issue field | Gives you the full name of the Jira user recipient. Note that this will not apply to external recipients! |
${emailaddress} | Non-issue field | Gives you the email address of the user recipient. |
${summary} | Issue field | Gives you the issue summary of the first issue in the notification. Handy in event mode! |
${key} | Issue field | Gives you the issue key of the first issue in the notification. Handy in event mode! |
${created} | Issue field | Gives you the issue created date of the first issue in the notification. Handy in event mode! |
${updated} | Issue field | Gives you the issue updated date of the first issue in the notification. Handy in event mode! |
${assignee} | Issue field | Gives you the issue assignee of the first issue in the notification. Handy in event mode! |
${assignee.username} | Issue field | Gives you the issue assignee username of the first issue in the notification. Handy in event mode! |
${assignee.fullname} | Issue field | Gives you the issue assignee of the first issue in the notification. Handy in event mode! |
${assignee.emailaddress} | Issue field | Gives you the issue assignee email address of the first issue in the notification. Handy in event mode! |
${issuetype} | Issue field | Gives you the issue type of the first issue in the notification. Handy in event mode! |
${priority} | Issue field | Gives you the issue priority of the first issue in the notification. Handy in event mode! |
${project} | Issue field | Gives you the project for the issue of the first issue in the notification. Handy in event mode! |
${reporter} | Issue field | Gives you the reporter of the first issue in the notification. Handy in event mode! |
${reporter.username} | Issue field | Gives you the issue reporter username of the first issue in the notification. Handy in event mode! |
${reporter.fullname} | Issue field | Gives you the issue reporter of the first issue in the notification. Handy in event mode! |
${reporter.emailaddress} | Issue field | Gives you the issue reporter email address of the first issue in the notification. Handy in event mode! |
${status} | Issue field | Gives you the status of the first issue in the notification. Handy in event mode! |
${resolution} | Issue field | Gives you the resolution of the first issue in the notification. Handy in event mode! |
${description} | Issue field | Gives you the description of the first issue in the notification. Handy in event mode! |
${environment} | Issue field | Gives you the environment of the first issue in the notification. Handy in event mode! |
${affected_versions} | Issue field | Gives you the affected versions of the first issue in the notification. Handy in event mode! |
${fix_versions} | Issue field | Gives you the fix versions of the first issue in the notification. Handy in event mode! |
${components} | Issue field | Gives you the components of the first issue in the notification. Handy in event mode! |
${labels} | Issue field | Gives you the labels of the first issue in the notification. Handy in event mode! |
${event.type} | Non-issue field | In event mode, you can use the event type like "updated" or "commented" in your notifications. Only available in event mode. |
${event.username} | Non-issue field | In event mode, you can set the username of the user firing this event. Only available in event mode. |
${event.fullname} | Non-issue field | In event mode, you can set the full name of the user firing this event. Only available in event mode. |
${lastcomment.body} | Issue field | Gives you the body of the last comment on the issue of the first issue in the notification. Handy in event mode! |
${lastcomment.time} | Issue field | Gives you the time of the last comment on the issue of the first issue in the notification. Handy in event mode! |
${lastcomment.author} | Issue field | Gives you the author of the last comment on the issue of the first issue in the notification. Handy in event mode! |
${customfield-name} | Issue field | Gives you a custom field value from a supported custom field. Replace <customfield-name> with the specific Custom Field Name. |
${customfield_XXXXX} | Issue field | Gives you a custom field value from a supported custom field. Replace XXXXX with the specific Custom Field ID. |
${jql} | Non-issue field | Gives you the JQL configured for the notification |
Non-issue field | Gives you the name of the notification | |
Non-issue field | Gives you the ID of the notification. Useful for creating links back to the notification for troubleshooting. VERSION 6.3.0+ | |
${notification.jql} | Non-issue field | Gives you the JQL configured for the notification |
${notification.description} | Non-issue field | Gives you the description of the notification |
${baseUrl} | Non-issue field | Gives you the Base URL of Jira with the context path. Useful for creating links to content in Jira. VERSION 6.3.0+ |
${issuecount} | Non-issue field | Total number of issues in the Notification. |