What happens when you swap settings for allowGlobal and allowRoom?

I have a HipChat integration that was originally developed to be installed per room (allowRoom == true, allowGlobal == false). Changing requirements have us moving to a global install  (allowRoom == false, allowGlobal == true).

What will happen to existing installs if this change is made in the capabilities descriptor?


1 answer

0 votes

When an integration is installed globally in a group, existing room-level installations will be removed. Is your integration listed in the Atlassian Marketplace? Note that changing the allowRoom/allowGlobal would not be handled by auto-upgrade and existing users would need to re-install/approve the add-on.

It is in the marketplace. Would existing users be prompted to re-approve or would we need to prompt them? If they don't upgrade, would the existing configuration continue to work (presuming we handle the situation on the backend, of course)?



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...

506 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