StatusPage Add-on integration is not working in Jira Service Management


アトラシアン コミュニティをご利用ください。


プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および Crucible は除く


The customer web portal channel in JSM does not display any visible links to the Status Update or Incidents from the StatusPage.


The issue may occur in any setup where one Jira instance makes an HTTP\s request to a StatusPage server.


When a Jira instance makes an HTTP\S request to a remote StatusPage server to retrieve the incident status, the request fails with messages similar to the following:

{"message":" Connection reset"}

Analysing the HAR file, we could observe the referrer URL '<JIRA_BASE_URL>/servicedesk/customer/portal/1' followed by the link address '<JIRA_BASE_URL>/rest/statuspage/1.0/config/project/status_page/10003' is unable to load or failing with the following error:

{"message":"org.apache.http.conn.ConnectTimeoutException: Connect to [] failed: connect timed out"}


In order to retrieve incidents from the StatusPage, Jira will send an HTTP outbound request over port 443, which is blocked by the firewall:

root@jiraapp:~# nc -vnz -w 1 443
nc: connect to port 443 (tcp) timed out: Operation now in progress


Allow outbound connections from Jira application server to the StatusPage server over port 443. A successful transaction will look like this:

root@jiraapp:~# nc -vnz -w 1 443
Connection to 443 port [tcp/*] succeeded!

After successfully establishing communication, a message will be displayed on the web portal channel in JSM to inform your customers about the incident:

最終更新日 2023 年 4 月 26 日


Powered by Confluence and Scroll Viewport.