How to modify the "Communications Breakdown" error message in Jira?
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The information in this page relates to customizations in Jira. Consequently, Atlassian Support cannot guarantee to provide any support for the steps described on this page as customizations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Also, please be aware that customizations done by directly modifying files are not included in the upgrade process. These modifications will need to be reapplied manually on the upgraded instance.
This page is for Jira Data Center
In this article, we will discuss - how to modify the "Communications Breakdown" error message in Jira. There are 3 different messages:
Solution
Modifying your Communications Breakdown message
To modify the content of the existing error message, the following steps can be performed:
Backup the file <Jira_INSTALL>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/JiraWebActionSupport.properties
Search and update the text field, which is defined after the variables in the file '<Jira_INSTALL>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/JiraWebActionSupport.properties'. Eg:
common.forms.ajax.error.dialog.heading=Communications Breakdown common.ajax.unauthorised.alert = You are not authorised to perform this operation. Please log in. common.ajax.servererror = The Jira server was contacted but has returned an error response. We are unsure of the result of this operation. common.ajax.commserror = The Jira server could not be contacted. This may be a temporary glitch or the server may be down.Restart Jira
⚠️ Since these configuration changes are performed in the Jira installation directory, any changes you make can be lost on the upgrade.
Was this helpful?