Create new Jira issues in Outlook
We’re adopting the new Atlassian Design Guidelines. This helps users which are new to Jira to feel right at home and fields can be filled out even more intuitively.
With our email integration, you can create or update issues directly from your emails, including attachments and text formatting like lists, colors, and tables. The interface is similar to Jira, allowing easy navigation. You can fill out necessary fields in Outlook, and your email content will be converted to Jira markup.

Click through demo
Feature at a glance
When receiving an email needing support from other teams, it helps to inform them quickly.
Create new issues based on emails incl. custom fields
With our Jira integration in Outlook, you can open the “new issue” dialogue via the icon at the top of your email to create an issue based on the email conversation.
Any custom fields defined in Jira are automatically taken over by the Outlook add-in. Some third-party apps (e.g., Tempo Timesheet or Jira Portfolio) are not supported: Supported custom fields
The dialogue/drop-down shows you all Jira projects you have access to. Based on the selected project type, the related issue types are provided in the drop-down.
If you select a sub-task issue type, the add-in opens a new field type issue. This will be the parent of your new sub task, allowing you to search for keys or descriptions filtered by the selected project.

Work with attachments
Outlook Email for Jira supports four types of attachments:
file attachments (e.g. when you forward an email, the email itself is an attachment)
inline images (e.g. signatures are oftentimes declared as inline images)
files from your local file system (e.g. pictures, excel sheets you wish to share with your colleagues)
the whole email as a file (.msg /.eml format) (e.g. emails from a supplier which is relevant for the project)
Via the Outlook settings, you can configure attachments to be automatically included by default when creating an issue. You can also manually select or remove attachments as needed or add attachments by dragging and dropping them from your device, or by choosing “All” or “None” in the dialogue box.

Email sharing
A shared email conversation is linked to your login. Other users will see it as you do. Logging out may break visibility for other Jira users.
You can share a conversation or email with those without inbox access in Outlook. After sharing to Jira, access shared emails in your issue in the related emails panel.

What do you want to share? | Just this email: Only the email will be shared, excluding other emails in the conversation. This conversation including future replies: The email and all related emails in the conversation will be shared, excluding drafts and deleted mails (moved to “Deleted Items” are still shared). |
Who should be able to see this? | Just myself: Only your personal logged-in Jira and Microsoft 365 users can see this shared item in Jira. Everybody in my company with access to this issue: A logged-in Jira user can see this item only if logged in with a Microsoft 365 account from the sharing user's organization. Every logged-in user with access to this issue: Any logged-in Jira user can see this shared item. |
Please note: When using the email feature in Jira, sharing and accessing email content is unavailable for Outlook exchange on-premise hostings. However, you can still use our Outlook add-in for the Outlook features.
Show notification next to email
Once an issue is created, a small notification “Jira” appears next to the email, helping you quickly identify conversations with corresponding issues in Jira.

Show email panel in Jira issue
When you access Jira through the link in the Outlook sidebar, you'll find the newly created issue and the associated email in the related emails panel. All essential information is organized and integral to the project.

Field Mappings
We use default values from Jira when possible. Learn more about our Field Mappings here.
The Outlook add-in offers customizable templates defined by the Jira admin, determining which email information is available in Jira. This is the default:
The email subject is automatically the summary of the Jira issue
The whole email body is the description of the Jira issue
The sender of the email is the reporter of the Jira issue
Jira Service Management specifics
The Outlook add-in offers features for Jira Service Management agents, allowing them to create tickets on behalf of the email sender.

Project and request type | The add-in will work with Request Types (instead of Issue Types). |
Tab: Service portal | It shows a tab called Service Portal that includes fields just as configured in your JSM portal. |
Tab: All fields | If you want to add information that is not visible for customers, you can use the tab “All fields”. |
Reporter field | The reporter field will check, if the sender of the email has a JSM account. If yes, our add-in allows to create a new one (if allowed by the portal settings). |
Email participants | Other persons on CC will be added as request participants when they have a JSM account. |
You can disable Service Portal fields in the settings under default settings.
Refer to this article on how to raise support tickets from Outlook via the Jira Service Management Portal in Outlook.
Troubleshooting: Don’t create customers automatically
At this time, we do not provide an option to completely remove this feature. However, you can disable it or find alternative solutions in several ways:
Remove the “Modify reporter” permission for your agents in Jira Service Management to prevent raising issues on behalf of customers.
Change the default template for the “Reporter” field from <SENDER> to <USER> to auto-fill the current Outlook add-in user as the default reporter.
Use the issue type instead of the request type to create new issues.
Manually remove the value for the “On behalf of” field when creating an issue.
COM add-in specifics
Create issues based on text
When using the COM add-in, you can select a text section in the email and create a new issue for only the selected text selection.
-20241218-103921.png?inst-v=a6fc8980-bb07-4fb7-860b-f3af06d7605f)
Notification (icon) on issue creation
When using the COM add-in, a separate Jira-icon next to your email will show you, that an issue has been created to this email (see green markup).
-20241218-104005.png?inst-v=a6fc8980-bb07-4fb7-860b-f3af06d7605f)
Outlook web is slightly different. Check this guide how to find the add-in online.
Feature configuration
To use Jira features in Outlook (like creating Jira issues from emails), a connection between Jira and Outlook must be established by your Jira and Microsoft admin (refer to: Admin configuration).
User configuration
Main configuration can be done via the Outlook settings by the user.
Admin configuration
To get started, the installation and deployment of our Outlook add-in (free) is necessary. This task should be carried out by the Jira admin and Microsoft admin. The Jira admin needs to prepare the set-up while the Microsoft admin deploys the add-in centrally to all users/team.
The installation process is straightforward and can be completed in a just a few clicks by following the instructions available within the Jira admin settings (in the first place).
Useful links
Further information as well as the technical reference on shared office items can be found here: Sharing access to Microsoft 365 items
Interested in managing emails within Jira? This functionality is available without specific prerequisites: Emails: Work with emails in Jira
Detailed explanation of the sharing options from Jira can be found here: Email: Work with Outlook emails in Jira