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

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)?

 

Thanks!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Mar 26, 2018 in Hipchat Data Center

Migration of Hipchat server to Data Center - a retrospective

Background While our Hipchat server environment was reliable and performing well, as a significant and growing part of our business, the need to leverage the benefits of Hipchat Data Center&nbs...

458 views 2 6
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