HipChat Server: JIRA Issue Preview is Not Working


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


プラットフォームについて: 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 は除く

This is for an outdated version of Hipchat Server

 This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.

When will my version be deprecated?

The following versions have been deprecated:

  • Hipchat Server 1.3 (EOL Date: Aug 17, 2017)
  • Hipchat Server 2.0 (EOL Date: Jun 17, 2018)
  • Hipchat Server 2.1 (EOL Date: Dec 8, 2018)

The following version will be deprecated soon:

  • Hipchat Server 2.2 (EOL Date: May 30, 2019)

You can read more about Atlassian's End of Life policy here.

You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.


The JIRA Issue Preview is not showing as expected on the configured rooms in HipChat clients when issue key is sent as a message.



  • HipChat Server 2.x connected to JIRA

Diagnostic Steps

  • Standard notifications are sent as per normal for all scenarios below:
  • Enable issue preview globally for all projects is checked:
  • The connection status in JIRA is shown as LIMITED . It means that Hipchat cannot make a connection back to JIRA Server.


The common cause to this problem is mentioned in the Hipchat limited connectivity in Jira Server article:

  • JIRA Server is behind a firewall that is preventing Hipchat from being able to contact JIRA Server
  • HipChat was configured with the wrong base URL


JIRA Server is behind a firewall

  • If you are hosting JIRA Server behind a firewall, you will not be able to get Jira Server into the CONNECTED state without putting JIRA on the other side of the firewall.
  • If HipChat cannot talk to JIRA via DNS name, manually edit the /etc/hosts file and add the JIRA hostname on the HipChat Server

JIRA Server isn't behind a firewall

  • It is likely that the hostname Hipchat is using to contact JIRA Server is wrong
  • You can check what hostname is being used by going to the integrations admin screen in HipChat https://www.hipchat.com/admin/addons
  • When you find JIRA Server in the list of addons you should be able to see the hostname of JIRA in the integration name.

If you are not using a fully qualified domain name when you connected the integration, HipChat will try to use that URL to contact JIRA Server.

最終更新日 2018 年 11 月 2 日


Powered by Confluence and Scroll Viewport.