Disabling the HipChat Integration with the Atlassian products
プラットフォームについて: 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 Atlassian products provide a number of integration points with HipChat. However, Atlassian has discontinued development on all chat products and HipChat Cloud services were shut down in February 2019, meanwhile Hipchat Data Center and Server will both reach end of life in September 2019.
If you're not using HipChat, you can safely disable the integration on your instance by following the steps below for each individual product.
ソリューション
Here are the steps to be performed to disable the integration for the various products.
Jira
First, please ensure you don't have any workflows that contain "Notify HipChat" post functions. Run this query on your database to identify affected workflows:
select * from jiraworkflows where descriptor like '%hipchat%';
JIRA will fail to start if you have any such defined HipChat post functions and the plugins are disabled on startup. If that happened and not able to restart Jira, please follow the resolutions noted in this KB article to enable the HipChat plugins. You may also see longer start times as Jira will still attempt to enable the plugins at startup.
Navigate to the JIRA Administration Page > Manage apps
Clink on the Manage apps menu and change the category from "User Installed" to "All apps"
Search for "HipChat"
Disable the following add-ons:
Atlassian Hipchat Integration Plugin
Atlassian Hipchat Integration Plugin Core
HipChat for Jira
Confluence
Navigate to the Confluence Administration Page > Manage apps
Change the category from "User Installed" to "All apps"
Search for "HipChat"
Disable only the
Confluence
Hipchat Integration Plugin
one, until the removal of Hipchat related plugins are being shipped in Confluence 7.0.
This is due to the dependency of the Emoticons plugin on theAtlassian HipChat Integration Plugin Code
app.
No other changes, including database queries or disabling of additional apps, is required.
Existing suggestion
In the meantime, we'd also encourage you to follow the improvement request ticket, in which will cover up-to-date news regarding the Hipchat plugins removal in Confluence:
- CONFSERVER-57602Getting issue details... STATUS
Bitbucket
Navigate to the Bitbucket Administration Page > Manage apps
Change the category from "User Installed" to "All apps"
Search for "HipChat"
Disable only the
Bitbucket Hipchat Integration Plugin
one
No other changes, including database queries or disabling of additional apps, is required.
What happens after the app has been disabled?
By disabling this apps, the following happens in Bitbucket:
the “Hipchat integration” menu item in the side bar of the administration page is removed.
the event listeners that trigger the HipChat messages to be sent are disabled so there is no attempt to send these messages to HipChat.
Impact on Emojis list
Bitbucket itself supports the standard smileys and the twemoji set of emojis.
Any additional emojis that were available when Bitbucket was integrated with HipChat will not be available anymore after disconnecting Bitbucket. This is because HipChat was the source for these emojis, including the custom ones.
Existing suggestion
This is the suggestion requesting for the removal of the integration in the product itself:
- BSERV-11665Getting issue details... STATUS