JIRA login to Hipchat

I'm trying to login to Hipchat, to integrate a Private room with a project.  But the Chrome console is throwing this error:

POST https://hailo.jira.com/rest/hipchat/integration/latest/oauth2/begin500 (Internal Server Error)batch.js?locale=en-UK:177





See screen cap: https://i.imgur.com/TR3ntGq.gif

3 answers

1 accepted

0 votes
Accepted answer

After some investigation we found out what the underlying problem is:

It looks like you have configured JIRA<->HipChat integration a while ago with the old version of the plugin. Since then we introduced a new version with a lot of additional features. With the new version of the plugin all previously configured notifications still work and you can use some of the newer nicer UI but to get access to the new features you would need to re-link your JIRA instance and the HipChat group.  You have hit a bug when we don't properly handle log-in functionality when the plugin was configured using the old way.

It takes 30 sec, just follow the prompts on https://changoinc.atlassian.net/plugins/servlet/hipchat/configure page as Elisa mentioned above. This is the relevant documentation page.

Anatoli, it looks like we have the same issue and before I update the plugin version, I wanted to know if it would affect my existing JIRA workflow-based hipchat integrations (which we have tons and want to continue to use those). Or the workflow hipchat integrations should continue to work seamlessly, in addition to fixed JIRA/hipchat integration at the JIRA projects level?

The workflow HipChat integrations will continue to work seamlessly!

Cool, do you have a link to a release notes or something that states that? We really can't afford to have a disruption for the workflow-based hipchat integrations. Also, if something does act up, i'm assuming we can't rollback to the older plugin version, right?

Paul, we don't actually explicitly say anywhere that we will not break the existing notifications (it's taken for granted we don't want to break any existing functionality). Re: ability to rollback and avoiding disruption. I know, sometimes it pays off to be a little paranoid. We did test this case before releasing the plugin; if you want to verify your own configuration, the best bet is to do it on a testing/staging server. It is not easy to roll back: you will need to downgrade the plugin and re-configure the integration the old way (with a token).

Thanks Anatoli, we can't do test/stage server since we're on the Cloud. SO we'll just have to do it.

0 votes

Hi Miles,

Can you please try removing the integration and then re-connecting it again. You need to be JIRA and HipChat admin to do that (it is under System -> HipChat integration):


This should fix the problem.

Hi @Anatoli Kazatchkov 

I'm facing the same issue. 

Will removing the integration also remove all the settings? I would like to avoid having to reconfigure everything after re-connecting it again.


Hi @Jules Minvielle, you wouldn't need to reconfigure anything if you remove and then re-connect the integration. The settings will be preserved. Also, depending on the version of the plugin you are using you can just go to <https://YOUR-JIRA/plugins/servlet/hipchat/configure>; and follow the steps there.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,950 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you