Bitbucket to Hipchat integration issue

Our Bitbucket server has a modified context path. We have inserted /bb/ into the context path.

So while we are able to get notification from Bitbucket the links written in hipchat to navigate back to bitbucket does not contain the correct path, since its only using the base domain name expecting navigation to begin at the root and not at /bb/.

is there a way to provide this context path to the configuration.

1 answer

This widget could not be displayed.
Ann Worley Atlassian Team Apr 19, 2017

The HipChat integration link uses the Bitbucket base URL. Please update the Bitbucket base URL (Specifying the base URL for Bitbucket Server) and rebuild the integration link. All new posts to rooms should then contain correct URLs back to Bitbucket. Old posts with incorrect URLs will not be updated but it should solve the issue going forward.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 10, 2018 in Hipchat

What should I think about when migrating HipChat to Slack?

...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...

425 views 1 10
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