The technical requirements for the add-in differ from device to device.
...
| Classical Windows Add-in | Modern Office Add-in | |
|---|---|---|
| Windows | - Outlook 2010, 2013, 2016 - .net Framework 4.5 - JIRA 6.0 or higher | - Outlook 2013, 2016 - Office 365 subscription or Exchange Server 2016 CU5 |
| Mac | n/a | - Outlook 2016, at least version 15.37 - Office 365 subscription or Exchange Server 2016 CU5 |
| Web | n/a | - Office 365 subscription orExchange Server 2016 CU5 |
| iOS | n/a | - Outlook Mobile App - Office 365 subscription |
Jira Cloud | Supported via direct connectionconnection 🔒 | Supported via Cloud Connectcloud connect 🌍 |
| Jira Server | Supported via direct connectionconnection 🔒 💡 Some SSO solutions may require additional configuration | Supported via direct connection if system uses SSL (https) 🔒 Supported via Cloud Connect cloud connect if system is publicly accessibleaccessible 🌍 💡 Some SSO solutions may require additional configuration |
Connection Types
🔒 Direct Connection
If technically possible, our add-in tries to establish a direct connection to the Jira system. This is always possible when using the classic Windows add-in, as it runs locally on the users computer and can open outgoing connections.
The modern add-in always runs in a browser context, even when used in the desktop & mobile versions of Outlook. Therefore it's subject to all restrictions of normal web apps. As Jira does not send CORS headers in a consistent and reliable manner, we need to rely on some other techniques.
Jira Server / Data-Center connection in modern add-in
When using our Jira for Outlook add-on on Jira Server, we have the possibility to extend Jira to a certain point. This allows us to use a direct connection, if the Jira
Jira Cloud connection in modern add-in
For Jira Cloud, we very limited in what we can do.