Email This Issue
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
Email This Issue - for Jira Server/Data Center
Email This Issue - for Jira Server/Data Center
  • ⬇️Start Here
  • Email This Issue - for Jira Server/DC
  • Features
  • Secure the email channel with Email This Issue
  • Comparing Email This Issue and Jira Server/DC
  • 🤓Documentation
    • Outgoing Emails
      • Sending manual emails
        • The difference between email editors
        • Enabling template categories so templates can be chosen on the Email screen
        • Mail Generation Queue (formerly called Event Queue)
        • Manual Email Default Settings
      • Sending issue filters by email
      • Email templates
        • Adding custom macro to email templates
        • Adding Email Audit Log to email templates
        • Adding fields to email templates
        • Adding issue comments to emails
        • Adding issue link information to your template
        • Adding issue operation links to the email
        • Adding a signature with a company logo to emails
        • Adding user properties to emails
        • Disabling links and avatars or icons in templates
        • Formatting Date and Time values
        • Using reply templates
        • Using Mail Body Initializer templates
        • Rendering templates within templates
        • Velocity Context in email templates
        • Formatting number values
        • Searching for issues in email templates
        • Changelog information in email templates
        • Canned responses
      • Contexts
        • Context Resolution Algorithm
      • Event Notifications
      • Distribution lists
      • Workflow post functions
      • Custom fields
    • Incoming Emails
      • Attachment Filtering
      • Next Generation Mail Handlers
        • Jira automation and Next Generation Mail Handlers
        • Using regular expressions
      • Classic Mail Handlers - Deprecated
        • Mail Handler Error Log
        • Step-by-step Classic Mail Handler to Next Generation Mail Handler migration aid
        • Field Rules
        • Phasing out the Classic Mail Handler
        • Comparing the Classic and the Next Generation Mail Handlers
    • Integrations
      • CRM for Jira
      • nFeed
      • Glass Documentation
      • API - Integration with other services
    • Administration
      • General configuration
      • Email Audit Log
      • Outgoing Mail Connections
      • Outgoing Mail Queue
      • Incoming Mail Connections
      • Incoming Mail Queue
      • Incoming Mail Log
      • Backup and restore settings
        • Backup and restore administration
          • Backup menu
          • Restore menu
        • Backup and Restore Tutorials
          • Backup and restore for empty email settings
          • Backup and restore only parts of a configuration
          • Backup and restore every setting in the same instance
      • OAuth2 Authorizations in Email This Issue
        • OAuth2 Client Credentials
        • Authorizing Email This Issue to access Gmail accounts
        • Authorizing Email This Issue to access Microsoft 365 accounts
        • Enabling OAuth2 Authorization in your Google Account
        • Enabling OAuth2 authorization in your Microsoft 365 account
        • Troubleshooting guides for Microsoft OAuth2 Connections
          • How to fix "Authorization Was Interrupted" error
          • How to fix "BAD User is authenticated but not connected" error
          • How to fix "401 Unauthorized" error
          • How to fix "key expires_in " error
          • How to fix "Need admin approval" error
      • Alerting via Webhooks
        • Webhooks
          • Configuring Slack to receive webhooks
          • Configuring OpsGenie to receive webhooks
        • Webhook execution logs
      • Email Security
    • Service management integration
    • JQL Functions
    • Top-level menu navigation
  • ☁️Server to Cloud Migration
    • Server to Cloud - Automatic Migration tool
    • Server to Cloud - Manual migration guide for Email This Issue
      • Overview of available features
      • Differences of the Server and Cloud user interface
      • Migrating Outgoing Settings
        • Migrating Templates
        • Migrating Notifications
        • Migrating Manual Email Defaults
        • Migrating Contexts
        • Migrating Canned Responses
        • Migrating Post Functions
        • Migrating Outgoing Mail Connections
      • Migrating Incoming Settings
        • Migrating Classic Mail Handlers
        • Migrating Next Generation Mail Handlers
        • Migrating Incoming Mail Connections
        • Migrating Incoming Mail Queue Settings
        • Migrating Incoming Mail Log Settings
      • Migrating Other Settings
        • Migrating OAuth2 Credentials
        • Migrating global default email settings
        • Migrating permissions for sending emails manually
        • Migrating recipient restrictions
  • ❓FAQ
    • FAQ
      • How to bypass workflow conditions
      • How to avoid email loops
      • How to control who to send emails to
      • How to customize Email From in outgoing emails
      • How to enable logging
      • How to install license keys
      • How to find out why the Email button is missing
      • How to obtain a community or non-profit license
      • How to prevent duplicate emails
      • How to remove old content from reply emails
      • How to send personalized emails to recipients
      • How to set up auto-reply or acknowledgment emails
      • How to track cases when you don't get any emails
      • How to view the log of incoming and outgoing emails
      • The iOS Mail app does not show attachments
      • How to route emails to projects
      • How to maintain email threads in Jira
      • How to fix issues with a corrupt index state
      • How to set polling interval for mail accounts manually
    • Tutorials
      • Configuring email approval
      • Customizing the email template used with manual emails
      • Enhance Jira Service Management with Email This Issue
      • Getting Started
      • Setting up an Email Help Desk
      • Setting up customized notifications
      • Setting up a Service Management with a Next-Gen Mail Handler
  • 🌪️Misc
    • Open Source Components
    • Pricing Updates
      • Pricing Update effective October 1st 2018
      • Pricing Update effective December 1, 2021
    • End of Support Policy
    • Security Advisories
      • Email This Issue Security Advisory 2020-02-18
    • Database Tables
    • Translations
  • 🆕Release Notes
    • Release notes
      • 9.x.x
        • 9.15.0 Jira 10 compatibility
        • 9.13.0 Improvements and Fixes
        • 9.11.0 Improvements and fixes
        • 9.10.0 Major improvements and fixes
        • 9.9.1 Improvements and fixes
        • 9.9.0.2 Major improvements and fixes
        • 9.8.0 Improvements and fixes
        • 9.7.0 Improvements and fixes
        • 9.6.0 Improvements and fixes
        • 9.5.0 Improvements and fixes
        • 9.4.0 Bugfixes
        • 9.3.3. Improvements and fixes
        • 9.3.2 Major improvements
        • 9.3.1 Automatic cloud migration
        • 9.2.2.1 Bugfixes
        • 9.2.2 Improvements and fixes
        • 9.2.1.3 Compatibility changes for Jira 9.0.0
        • 9.2.1 Major improvements
        • 9.2.0 Improvements and fixes
        • 9.1.1 Improvements and fixes
        • 9.1.0.1 Alerting and other major new features
        • 9.0.2 Bugfixes, next step in deprecating the Classic Mail Handler
        • 9.0.1 Minor improvement and fixes
        • 9.0.0 Major improvements
        • 9.12.0 Improvement and fixes
        • 9.17 Improvements and Fixes
        • 9.18.0 Improvements and fixes
      • 8.1.x
        • 8.1.3 Classic handler is deprecated, timezone support, bug fixes
        • 8.1.2 Important bug fixes
        • 8.1.1 Microsoft 365 OAuth2, improvements and fixes
        • 8.1.0 Microsoft 365 OAuth2, improvements and fixes
      • Up to 8.0.6
Powered by GitBook
On this page
  • Render comments in emails using templates based on themes
  • Render Comments in emails using traditional templates
  • Accessing all comments (even restricted ones)

Was this helpful?

  1. 🤓Documentation
  2. Outgoing Emails
  3. Email templates

Adding issue comments to emails

PreviousAdding fields to email templatesNextAdding issue link information to your template

Last updated 1 year ago

Was this helpful?

The default email template of Jira Email This Issue is prepared to render comments into the email body when the Add comments to outgoing emails option is enabled. However, if you develop your own custom email template not based on the default template, you'll have to add velocity template code to render the comments.

In order to add issue comments to the outgoing emails, two requirements must be met:

  • The option "Add comments to outgoing emails" has to be enabled in the corresponding component:

    • Email button (under OUTGOING EMAILS --> Manual Email Defaults --> Comments settings. Read more here.)

    • Bulk Email (under SETTINGS --> General Configuration --> Comments settings. Read more here.)

    • Post Function (under Issues --> WORKFLOWS --> Workflows. Read more here.)

    • Event Notification (under OUTGOING EMAILS --> Notifications --> Email settings. Read more here.)

  • A template fragment has to be added to your email template that will render the comments.

The template fragments are different for HTML and TEXT emails. You can use the Field Picker dropdown and select Comment.

Render comments in emails using templates based on themes

The new email template themes make it possible to render comments in emails easily in various ways.

Comment rendering macro
Description
Order

#renderComments($!issue)

Renders all comments of the issue which are not restricted to groups or roles nor are internal comments in Service Management.

Ascending

#renderCommentsInReverseOrder($!issue)

Renders all comments of the issue which are not restricted to groups or roles.

Descending

#renderServiceDeskPublicComments($!issue)

Same as #renderComments($!issue)

Ascending

#renderServiceDeskInternalComments($!issue)

Renders Service Management internal comments of the issue

Ascending

#renderAllComments($!issue)

Renders all comments of the issue. Comments may be internal or public, restricted or visible to all.

Ascending

#renderLastComment($!issue)

Renders the last comment entered in the issue

#renderComment()

Renders the comment entered during the operation

#renderCurrentComment()

Alias of #renderComment()

#renderIssueComments(<sorting> <number of comments> <restrictions>)

Generic, multi-purpose comment rendering macro. SINCE 8.0.3

Parameters:

<sorting>: asc or desc

<number of comments>: an positive integer number or all to render all comments matching <restrictions>

<restrictions>: comment restrictions. Its values are:

  • empty: render all comments regardless of the restrictions

  • none: render comments which are not limited to groups, roles or which are not internal in Service Management

  • public: render Service Management public comments

  • internal: render Service Management internal comments

Render Comments in emails using traditional templates

Comments in HTML Emails

It is possible to fully control how the comments are rendered in the email. The following codeblock example renders comments in HTML:

#if ($!emailDef.emailOptions.addComments)
<tr valign="top">
    <td style="color:${textColour};font-family:${textFontFamily};font-size:${textSize};padding:0 10px 10px 0;white-space:nowrap;">
        <strong style="font-weight:normal;color:${textSubtleColour};">#text("common.words.comments"):</strong>
    </td>
    <td style="color:${textColour};font-family:${textFontFamily};font-size:${textSize};padding:0 0 10px 0;width:100%;">
        #foreach ($comment in $!publicComments)
        <p style="border-bottom: 1px solid #DDD;">
            <p style="font-weight: bold"><a href="$!baseurl/secure/ViewProfile.jspa?name=$!{comment.author}"><b>$!{comment.authorFullName}</b></a> - <b>$!{dateformatter.format($comment.created)}</b></p>
            <p>$!{rendererManager.getRenderedContent($!commentRendererType, $!comment.body, $issue.issueRenderContext)}</p>
        </p>
        #end
    </td>
</tr>
#end

Comments in Text Emails

It is possible to fully control how the comments are rendered in the email. The following codeblock example renders comments in Text:

-------------------------------------------------------------------------------
#if ($!emailDef.emailOptions.addComments)
$i18n.getText("common.words.comments"):
#foreach ($comment in $!publicComments)
$!{comment.authorFullName} - $!{dateformatter.format($comment.created)}
------------------
$comment.body
#end
#end

Reverse Comment List

Normally comments are rendered by date ascending. To render them the latest on top, you must reverse the list:

#set($publicComments = $!jetiFieldRenderer.reverse($!publicComments))

Last Comment

In operations when the users enter a comment (like issue update, or workflow transitions), the comment they enter can be referred to as $!comment or $!htmlComment depending on the content type of the template. In other cases, after reversing the comment list, you can access the last one easily:

#if($!publicComments && !$!publicComments.empty)
  #set($lastComment = $!publicComments.get(0))
  ...
#end

Without reversing the list first, access the last comment as:

#if($!publicComments && !$!publicComments.empty)
  #set($lastComment = $!publicComments.get($!publicComments.size()-1))
  ...
#end

Accessing all comments (even restricted ones)

To access all comments of an issue, use the $commentManager object.

#foreach ($comment in $!commentManager.getComments($!issue))
...
#end