• Update dependencies to the latest versions.

• Update dependencies to the latest versions.

• Update dependencies to the latest versions.

• Update dependencies to the latest versions.

• Update dependencies to the latest versions.

• Update dependencies to the latest versions.

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

• Support additional security checks required for Jira 9.0 and above.
• Additional logging

In previous versions of the app, we used an API to discover the address of the incoming email channel for the service desk project.

Unfortunately, a change in the API means that we can no longer use this to set the Reply-To address for outgoing notification emails sent by the app.

By default, outgoing emails will now use the From address specified in the Jira Outgoing Mail settings.

Additional admin settings have been added to the app's project settings page to set a default Reply-To address for the project and optionally additional request type-specific addresses.

Once upgraded, please review the app's project settings and refer to our documentation.

In previous versions of the app, we used an API to discover the address of the incoming email channel for the service desk project.

Unfortunately, a change in the API means that we can no longer use this to set the Reply-To address for outgoing notification emails sent by the app.

By default, outgoing emails will now use the From address specified in the Jira Outgoing Mail settings.

Additional admin settings have been added to the app's project settings page to set a default Reply-To address for the project and optionally additional request type-specific addresses.

Once upgraded, please review the app's project settings and refer to our documentation.

In previous versions of the app, we used an API to discover the address of the incoming email channel for the service desk project.

Unfortunately, a change in the API means that we can no longer use this to set the Reply-To address for outgoing notification emails sent by the app.

By default, outgoing emails will now use the From address specified in the Jira Outgoing Mail settings.

Additional admin settings have been added to the app's project settings page to set a default Reply-To address for the project and optionally additional request type-specific addresses.

Once upgraded, please review the app's project settings and refer to our documentation.

In previous versions of the app, we used an API to discover the address of the incoming email channel for the service desk project.

Unfortunately, a change in the API means that we can no longer use this to set the Reply-To address for outgoing notification emails sent by the app.

By default, outgoing emails will now use the From address specified in the Jira Outgoing Mail settings.

Additional admin settings have been added to the app's project settings page to set a default Reply-To address for the project and optionally additional request type-specific addresses.

Once upgraded, please review the app's project settings and refer to our documentation.

• In rare circumstances, the app was failing to start automatically, requiring a manual start.

• In rare circumstances, the app was failing to start automatically, requiring a manual start.

• In rare circumstances, the app was failing to start automatically, requiring a manual start.

• In rare circumstances, the app was failing to start automatically, requiring a manual start.

• In some circumstances, dollar signs ($) and backslashes (\) in comment text prevent notification emails from being sent.

• In some circumstances, dollar signs ($) and backslashes (\) in comment text prevent notification emails from being sent.

• In some circumstances, dollar signs ($) and backslashes (\) in comment text prevent notification emails from being sent.

• In some circumstances, dollar signs ($) and backslashes (\) in comment text prevent notification emails from being sent.

• Using height or width properties on images resulted in broken images in emails.

• Using height or width properties on images resulted in broken images in emails.

• Using height or width properties on images resulted in broken images in emails.

• Using height or width properties on images resulted in broken images in emails.

• Easy Email Attachments for Service Desk is now supported on Data Center deployments of Jira Service Desk.
• Minor form token handling fix.

• Easy Email Attachments for Service Desk is now supported on Data Center deployments of Jira Service Desk.
• Minor form token handling fix.

• Easy Email Attachments for Service Desk is now supported on Data Center deployments of Jira Service Desk.
• Minor form token handling fix.

• Easy Email Attachments for Service Desk is now supported on Data Center deployments of Jira Service Desk.
• Minor form token handling fix.

This release addresses several issues around non-Latin1 character sets — for example, Cyrillic, Czech, Hungarian, etc.

• Subject lines containing these characters were incorrectly encoded as HTML character escape codes. For example, the character Á would be shown as & #xC1;
• Email body text was incorrectly encoded resulting in ? characters being displayed instead of non-Latin1 characters.
• Please note that attachment file names are encoded using the Jira system encoding setting (System > System info > System Encoding) by the Atlassian Java API, depending on the character set and the receiving email client, these characters can be displayed incorrectly.
• It is recommended to run your system in UTF-8 across the database, application server and web application. Please see this Atlassian knowledge base article: Troubleshoot character display issues in Jira server.

Additionally, some template variables were being incorrectly expanded in the text of the email resulting in HTML tags being visible.

This release addresses several issues around non-Latin1 character sets — for example, Cyrillic, Czech, Hungarian, etc.

• Subject lines containing these characters were incorrectly encoded as HTML character escape codes. For example, the character Á would be shown as & #xC1;
• Email body text was incorrectly encoded resulting in ? characters being displayed instead of non-Latin1 characters.
• Please note that attachment file names are encoded using the Jira system encoding setting (System > System info > System Encoding) by the Atlassian Java API, depending on the character set and the receiving email client, these characters can be displayed incorrectly.
• It is recommended to run your system in UTF-8 across the database, application server and web application. Please see this Atlassian knowledge base article: Troubleshoot character display issues in Jira server.

Additionally, some template variables were being incorrectly expanded in the text of the email resulting in HTML tags being visible.

• New logo
• Compatibility with the latest versions of Jira and Jira Service Desk

• New logo
• Compatibility with the latest versions of Jira and Jira Service Desk

• Minor character encoding fixes.

• Minor character encoding fixes.

Version 400000000 - Released 2020-06-10 - Paid via Atlassian - Commercial

This is the first release. There are two functionally equivalent versions of the app, please use the correct version:

• 4.x.x supports Jira 8.x.x
• 3.x.x supports Jira 7.8.0-7.13.13

Key features

• Customers receive real attachments in their email client, no more portal links
• Easy to setup
• Agents work as usual with no changes to the Jira Service Desk comment interface

Documentation update