Outlook set-up
Great, that you decided for the Email feature! In order to use its full potential, please follow the steps below to finalize its set-up.
1. Application link
JIRA CLOUD ONLY
The application link is a secure way to connect your Jira Cloud instance with Outlook.
As soon as the Jira admin activated the email feature, an application link needs to be created.
The Outlook app uses OAuth 1.0a to connect to your Jira instance.
You need to create a new application link, so Outlook can connect safely.
You find more details about application links here.
For Jira Server/Data Center the link is created automatically after the installation.
2. Create application link
JIRA ADMIN
Please follow the instructions carefully!
Any misspelling could prevent Jira for Outlook from working correctly.
Overview
Step-by-Step
3. Install and deploy the Outlook add-in
MICROSOFT 365 ADMIN
The email feature only unfolds its full potential, if the correct Outlook add-in is installed.
The installation of the Outlook add-in is a prerequisite to use Jira features in your Outlook inbox (see below “Why Outlook add-in” for more information).
Alternatively, let your users install the add-in by themselves USER
Tip: Make sure to install the Outlook add-in to all those users, who work with emails a lot (and most probably need) to bring them to Jira.
Otherwise, Jira user’s won’t be able to access emails in the issue in the first place.
Why Outlook add-in
Outlook add-in required
With the add-in you can access Jira features in your Outlook inbox and thus, bring emails to Jira.
Only with the Outlook add-in you can:
Create issues right from your Outlook inbox
Search for related issues in the sidebar
Work with emails in Jira (share conversation)
Outlook add-in not required
Without the add-in you can “only” access Outlook features in Jira and see related emails in Jira.
Not every user in your team needs to necessarily install the Outlook add-in.
The following features can still be used without an add-in:
See issue-related emails in the Jira issue
Start new or answer back on emails from the Jira issue