Table of Contents | ||
---|---|---|
|
Hello! This guide will take walk you through all the configuration necessary configurations to get achieve the best Jira email integration possible. This The process will take 20-35 minutes, depending on what the specific features you needrequire.
Prerequisites
In order to successfully complete this guide, you will need the following:
An active Jira Cloud instance that you have administration rights for
For To process inbound email processing:
A Jira project
An external (non-Atlassian) mail source, for example a POP or IMAP server visible by JEMHC - Setup JEMHC Inbound mail (typically through a cloud provider like Microsoft 365 or Gmail, but could be your own).
For To send outbound email notificationnotifications:
An external (non-Atlassian) SMTP mail server.
Info |
---|
JEMHC does not support Atlassian Cloud default Mailboxes at all. Atlassian does not support 3rd party usage and periodically rotates the credentials in any case. |
Installing the app
First, we will show you how to install JEMHC on your Jira Cloud instance. Open the Apps drop-down menu from the top Jira navigation bar. Click Find new apps.
...
On the app search screen, search for the term 'JEMH'. In the search results, you should see Enterprise Mail Handler for Jira (JEMH). Clicking the search result item will show you a Marketplace listing for the app.
...
Click the Try it free button to begin an evaluation of the app. Atlassian will then ask for confirmation.
...
After confirming, JEMH the app will then be installed. This could take a minute so please wait!
...
Once installation is complete, use the Get started link to open JEMH Cloud startup wizard, which will assist you with creating a basic configuration.
...
JEMH Cloud Outgoing IP addresses
Region | Current | From February 1, 2024 | USA | ||
---|---|---|---|---|---|
Code Block | IP addresses to allow | ||||
USA |
| Germany | n/a | ||
TODOEU (Frankfurt) |
|
Note |
---|
Always ensure that access your mail server is adequately secured! |
Next we will configure JEMHC to process emails retrieved from an incoming mail server. Firstly, we will select a project that emails should create issues in. Later on you can add additional projects to the configuration - this is just for initial set up. You will also be asked for an issue type.
...
Expand | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
...
Until the mail server setting has been used, its status will be 'unknown'. To validate this, use the ▸ ping action, loacated under the … more actions icon. Here, the outcome is that the SMTP server is now Online (this would have happened anyway on first actual usage):
...
Recent outbound notifications can be reviewed through: Auditing > Outbound Messages, you can see the outbound message configuration tests sent using ▸ ping.
...
The Auditing > Events view shows the webhook events sent by Jira, and indicates whether they were handled or not. Any Jira issue actions that trigger events matching the selected notification mapping(s) will be shown in the Events view:
...