So we are considering trying out hipchat in our organization which consists of a few thousand people, and a good 200+ people would be using hipchat.
We would have dozens of different teams, you usually would be a member of lets say at least 3-4 teams concurrently.
How are other organizations working around the limitation that you have to use a different email adress to sign up for different hipchat groups?
Surely just using a single group would be a nightmare in terms of administration (eventhough we would be using LDAP directory since we'd host hipchat server by ourselves).
The only other workaround I can imagine is having to write a little webapp that lets you choose from the list of known hipchat groups and then creating and registering an alias email adress at our exchange server.
Still a stupid workaround for an extremly bad architecture decision.
Any bigger user groups out there that dare to share their experiences/workarounds?
...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...
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!
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