問題

While we have the convenience of integrating Hipchat Data Center / Server with Jira for collaboration and faster resolution to issues, we might run into roadblocks when setting them up or even maintaining it. Some of the common known issues include:

1. We couldn't reach your server error on the web interface

2. Can't integrate two Jira instances with the same Hipchat Data Center / Server

3. Jira issues in private projects are previewed in Hipchat

診断

Issue #1

• Verify connectivity between Hipchat Data Center / Server with the Jira instance via telnet on port 443 from the machine hosting Jira and you will be presented with the following error:

  $ echo | telnet hipchat.example.com 443
  Trying 111.11.11.111...
  telnet: connect to address 111.11.11.111: Connection refused
  telnet: Unable to connect to remote host

  
  At the same time, the installation will fail right away when you enter the Hipchat FQDN in the installation screen.
  

• Hipchat is running on a non-signed SSL certificate. If you enter the URL preceded by https, Jira will report the same error as when it's unable to reach Hipchat on 443. A closer look at the Jira logs will show an SSLHandshakeException. which is similar to the Cannot integrate Hipchat Server with Confluence or Jira with SSLHandshakeException KB

  If you enter the URL preceded by http, Jira will connect fine since NGINX on the Hipchat side will handle the redirection. The user will confirm the installation on the Hipchat side but it will fail later at the time of installing the integration on the Jira side because it will try connecting via SSL. The same SSLHandshakeException will be visible in the logs. 

• Java is using an old TLS version. Starting from version 2.0.7, Hipchat Data Center / Server does not support TLSv1. If Jira tries to connect using TLSv1, it will fail and report that Hipchat is unreachable. 

  More details can be found in 

Issue #2

The symptom of this issue is that the Hipchat integration with Jira-A will be removed when you integrate Jira-B with Hipchat. 

Issue #3

The Hipchat integration disregards the Jira security model. If you have the integration enabled, you run the risk that you could expose ticket names to users who have the link but might not have permissions to see the actual ticket. 

原因

• Issue #1

  Connection between the 2 applications are blocked because port 443 is not opened, which is an essential requirement for integration to properly as mentioned in the Troubleshooting Failed Integration Installations

• Issue #2

  The integration is installed in Hipchat Server based on the plugin key, which is a function of the server ID. It's not possible to integrate two Jira instance with the same server ID to Hipchat Server.

  One will overwrite the other once it finds the plugin key in the database is the same. 

• Issue #3

  This is the current limitation of the integration where you do not have the ability to limit the visibility of issues according to the Issue Security Level

ソリューション

Issue #1

• Ensure that you have the port 443 opened for both applications to be able to communicate with each other and transfer information.
• Utilize a valid CA signed SSL certificate on your Hipchat Server. If you run into issues with the SSL certificate, go through the potential causes and solution in Hipchat Server SSL Installation and Troubleshooting Guide.
• Update the Java startup properties in setenv.sh/sentenv.bat as mentioned in the Integration unable to reach Hipchat Server 2.0.4 or 2.0.7+ with SocketException: Connection reset.

Issue #2

Change the Jira server ID and re-install the two integrations on the 2 Jira instances.

Issue #3

Feature requests to fix this behaviour are logged in the public bug tracker: 

• HCPUB-1551 - Hipchat integration "Enable issue preview" - per room TO BE REVIEWED
• HCPUB-2616 - Filter Jira to Hipchat notifications based on issue security level TO BE REVIEWED