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
  • Email screen actions
  • Executing workflow transitions

Was this helpful?

  1. Documentation
  2. Outgoing Emails

Sending manual emails

PreviousOutgoing EmailsNextThe difference between email editors

Last updated 9 months ago

Was this helpful?

One of the key features of Jira Email This Issue is sending manual emails right from the Jira issue's screen.

To send a manual email, do either of the following:

  • Click the Email button on the right side of the issue screen.

  • Under More, choose the Email This Issue item from the menu.

  • Press Q.

Note: Email templates, and SMTP server settings don't need to be set each time. However, if the default settings are not enough, you can define manual email configuration sets that override the defaults and allow you to fully customize how you want to send emails manually.

To learn more about the default procedure of sending them from the issue, read forward.

Email screen actions

The email screen is where you can compose emails manually the following way:

  • Set recipients (To, Cc, Bcc). Recipients can be users, roles, groups, custom fields, external email addresses and virtual users (e.g. project lead, watchers, assignee, reporter).

  • Enter an email subject and email body.

  • Add attachments to the email.

  • Choose from predefined messages to add complex content to the email body.

On the right side of the email screen you can see the issue details on the right hand side for easy reference, therefore there is no need to open the issue in a separate tab of the browser.

Email options

While composing your email, you can set various email options. Click the Email options button on top to reveal or hide them on the right side panel of the screen.

The email body

You can compose an individual message in the editor or you can fill the email body with predefined content. Choose the predefined response from the drop-down list, and click Add Response for it to appear in the body.

Important: Never use the same templates to prefill body and send emails. Mail Body Initializer templates are purely used to initialize the Body field in the email screen. When the email is sent, the formatted, preinitialized and possibly modified Body will be submitted as if it was entered manually.

Therefore the template used for generating the final email will include this formatted, rich body value via the $!mailBody variable. This means, if you used the same template, the preformatted content may be added twice to the email.

If you use a prefill template, the email template you send with may be as simply as the $!mailBody variable.

Large images in the email body

When adding large inline images to the email body please wait until the uploading progress bar reaches 100% and then fully disappears before clicking on the Send button. In case of clicking Send earlier 500 - internal server error occurs.

When using Reply/ Reply all / Forward function to send emails containing large inline image(s) loading the Manual Email screen might take up to a few minutes depending on the inline image's size.

The Email Template field

The email template used for formatting email is determined by the project and/or the type of the issue (via Contexts) and can be easily configured using the built-in template editor.

Contexts may be configured with multiple template categories. Templates from the selected categories are listed in the email screen. Emails are generated from the selected template.

The Subject field

Clicking the refresh button next to the Subject field regenerates the subject according to the template. Once clicked, the page will reload to display the content generated by using the selected template.

Attachments

You can select the issue attachments you want to attach to the email either in the text editor, or in the Attachments field.

You can also add additional files to your email for your recipients to receive all necessary information in the Attach more files field.

Quote comments in mail body

The right hand side of the email screen shows the issue details including the comments visible to the current user. Comments may be quoted in the mail body with a single click.

Email preview

Once you have composed your email recipients, subject, body and options, you can preview what the email will look like for the recipients.

To preview, click the Preview button at the bottom.

Note: Email recipients are resolved to email addresses.

The Send & Remember settings button

Email options are preset from the global defaults, but can be overridden using the Send & Remember settings button. These user preferences are reused next time you send emails.

Note: These preferences used to be stored in Browser cookies. Since Version 8.1.0, user preferences are stored in the database so they are not lost if users change browsers or clear browser caches.

If you choose, Send & Remember settings, the email recipient configuration is also stored and reused next time.

Executing workflow transitions

Jira Email This Issue for Server supports the execution of workflow transitions right after sending emails manually. To activate this feature, the Jira administrator must prepare the workflow.

Transitions marked by a transition property jeti.on.send.email.transition with the value true are executed.

  • If no transitions are marked in the current status, no transitions are executed automatically.

  • If only one transition is marked in the current status, this transition is executed automatically.

  • If multiple transitions are marked in the current status, when sending the email a popup screen is shown to select the transition to be executed. Skip transitions by selecting Send Email Only.

Note: Keep the following in mind:

  • The transition screen is not shown unless the transition is configured to show a pop-up window.

  • Conditions are not bypassed, and validators are applied.

  • The selected transition is executed after the email is sent. The failure to send the email skips the transition. Although, the failure to execute a transition does not prevent the emails from being sent.

Note: It is a good practice to add transitions to the workflow statuses that are hidden from the user interface and are executed only when emails are sent.

For more information about setting up an SMTP server, see .

For customizing default settings, see , , .

To initialize the email body, you need to develop an email template first under Templates and when adding a new or editing and already existing Context, select it the Mail Body Initializer Template field. Read more about it .

See , and for more information.

See , and for more information.

See , and for more information.

For more information, see .

🤓
Outgoing mail connections
Manual email default settings
Email issue filters
Email Templates
here
Email templates
Contexts
Email editors and Rich Text emails
Email templates
Contexts
Email editors and Rich Text emails
Email templates
Contexts
Email editors and Rich Text emails
Workflow post functions
Progress bar should fully disappear before sending an email