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
  • Context attributes
  • Adding a new context
  • Enabling/disabling contexts

Was this helpful?

  1. Documentation
  2. Outgoing Emails

Contexts

PreviousCanned responsesNextContext Resolution Algorithm

Last updated 9 months ago

Was this helpful?

Contexts connect various configurations and settings to a scope. The scope of a context can be composed of:

  • A project (optional)

  • An Issue Type (optional)

  • A JQL filter (optional)

The scope determines which issues the Context is applicable for based on the . These are displayed in the Contexts menu in an expandable list.

Context attributes

Context attributes have the following main aspects:

  • The scope for which the context is set (project/issue type/JQL)

  • The content that is applicable to the scope

  • The Email This Issue notifications applicable to the scope

  • Additional settings within the scope

Adding a new context

To create a new Context do the following:

1. Go to OUTGOING EMAILS --> Contexts.

2. Click the Add button.

Scope

The scope maps all the context settings to a certain project/issue type/JQL or a combination of these.

Attribute
Description

Project

Defines the project to which the context is applied. Applied to all projects if left empty.

Issue Type

Defines the issue type to which the context is applied. Applied to all issue types if left empty.

JQL Filter

Defines a JQL condition to match the set of issues the context may be applied to. JQL Filter with a combination of Project and Issue Type selected is used to determine if the Context is applicable to an Issue being sent in an email.

Description

A description of the Context.

Order

Content and Notifications

The content of a context specifies templates and canned responses to be used when sending manual emails.

Attribute
Description

Template

Mail Body Initializer Template

Template Categories

Notification

Note: Either a Template or a Notification is mandatory. You cannot create "empty" contexts without at least either one of these.

Additional Settings

Additional content settings allow you to further configure options for your outgoing emails.

Attribute
Description

Field for External Watchers

Sender Name Pattern

A velocity markup pattern or a static text to format a sender name in outgoing emails. E.g. if you don't want to show the name of real users as the sender of emails, you can include the project name or the value of a custom field.

Note: Not all SMTP servers allow for this setting. Please check your SMTP server options for confirmation.

From Address Pattern

Velocity markup pattern or a static email address to format the From Address in outgoing emails. E.g. if you don't want to show the name of real users as the sender of emails, you can include the project name or value of a custom field.

Note: Not all SMTP servers allow for this setting, please check your SMTP server options for confirmation.

Reply-To Address Pattern

Velocity markup pattern or a custom email address to format the Reply-to Email Address in outgoing emails. This is very useful if your IMAP and SMTP server addresses are different.

Bcc Address

A single email address, if specified, will be added as a Bcc recipient in all emails sent via this Context.

Email Details in Comments

Option to set whether comments should include the email details (such as To:, From:, Attachments in the email etc.). This option is about comments that are created from manual outgoing emails and added to the issue.

Send Individual Emails

Enable this if you want each recipient to receive a separate email instead of sending a single email to all recipients.

Learn more about this feature

SMTP Connection

Select the SMTP connection to be used to deliver emails via this Context. Default is Jira's outgoing mail setting. SINCE 7.1.1.17

Email Headers

Custom Email headers of outgoing emails may be set using this attribute. The field should contain email headers in the format of headername:headervalue, multiple headers should be entered one per line.

SINCE 8.0.6

Enabling/disabling contexts

Contexts may be disabled and enabled again. This allows admins to test their configuration without having to remove or change contexts. Disabled contexts are disregarded in the context resolution algorithm explained above.

Defines the order in which the Contexts configured with the same combination of Project and Issue Type are evaluated (see examples ).

Defines the default email template that Jira Email This Issue will use when emails are sent. The template selected here is not visible on the email screen's editor, it can be thought of as a frame for your emails. Read more .

A template used for initializing the email subject and body on the email screen. Read more .

Categories are groups of email templates. Once selected here, users are able to choose a template from the given category on the email screen's dropdown list. Read more .

Defines issue event notifications for the context. They can work alongside Jira Notification Schemes, and allow you to fully customize notifications. Read more .

A text custom field where non-Jira user email addresses will be saved if the "Add recipients to watchers" option in Manual Email Default settings is enabled. Read more .

🤓
here
here
here
here
here
here
Context Resolution Algorithm