Versions Compared

Old Version 57

changes.mady.by.user Mike Harrison

Saved on

compared with

New Version 58

changes.mady.by.user Mike Harrison

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel3

...

Hello! This guide will take you through all the configuration necessary to setup JEMH for Jira Cloud (JEMHC)get the best Jira email integration possible. This will take 20 - 35 minutes depending on what features you need.

Prerequisites

...

...

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.

In order to successfully complete this guide, you will need the following:

  • An active Jira Cloud instance that you have administration rights for

  • For inbound email processing:

    • A valid 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 O365, Microsoft 365 or Gmail, but could be your own).

  • For outbound email notification:

    • 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 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 , search for the term JEMH using the search field provided. 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.

...

Expand
titleCreate Message Source configuration assistance

Setting

Description

Name

Name of the message source

Type

Message source type

Preset

Presets which can be used to simplify the remaining configuration i.e. Host/Post

Host

Message Server's hostname or IP Address

Port

Message Server's port

Timeout

Connection to be timed out based on the configured time (seconds). Leaving this configuration blank would result the timeout to be 30 second

Username

Username to access the account

Password

Password to access the account

SSL

Does the connection use SSL?

SSL Certificate Validation

SSL Certification Validation

Check Server Identity

RFC 2595 specifies additional checks that must be performed on the server's certificate to ensure that the server you connected to is the server you intended to connect to. This reduces the risk of 'man in the middle' attacks.

Read Strategy

Read Unread and Mark As Read - Only the unread emails in the mailbox are to be processed and once read, they will be flagged as read (Default). 

Read All and Delete - All the emails in the mailbox will be read and deleted after they are successfully processed.

NOTE:

  • You should be fully aware of the changes you make when switching between strategies as it can potentially impact your allowance.

For example: UserA has been using Read Unread and Mark As Read read strategy for past 5+ months and currently has over 2000 emails residing in the inbox. However, the user has now decided to switch the read strategy over to Read All and Delete and the consequence of this turned out that all the mails residing in the inbox folder were processed by JEMHC which resulted to exceeding the allowance. 

  • Potential impact - POP Mail Server configuration may override the instructions given by JEMHC.

For example: read strategy (in JEMHC) has been set to Read Unread and Mark As Read and the Mail Server (POP) has been configured to Delete Gmail's copy once it has been processed. The end result of this would be the processed mail will be deleted from the inbox as per configuration.


...

Until the mail server setting has been used, its status will be 'unknown'.  To validate this, use the poll action ▸ to test. Here, the outcome is that the SMTP server is now Online (this would have happened anyway on first actual usage):

...