Account Management Best Practices

My organization does a lot of consulting work, which means we work in lots of different instances of various Atlasian products (JIRA, HipChat, Bitbucket, etc.) for different customers. We're really struggling with the whole Atlassian ID concept. Just now I stumbled on the whole "personal vs. managed account" concept and I am ready to throw in the towel.

Can someone please give a recommendation of the best way to set up users when you need to work in mulitple instances? Is this use case handled in any way by the newest Atlassian ID Rollout? I have looked but I can't find a clear answer anywhere.

1 comment

This helps with your use case only if the different instances of Atlassian products you use are Atlassian Cloud instances.

As the Cloud instances get upgraded to use Altassian Account for login, you'll be able to use your Atlassian Account (https://id.atlassian.com) credentials to login to all the sites, rather than having to remember a different username and password for each instance.

If the Atlassian products you are logging into are server products, then they are not affected by this.

That seems logical in theory but doesn't work for us in practice. The biggest issue right now is HipChat. Logging into the web interface for alternate instances doesn't seem to recognize Atlassian ID in all cases. The other issue we run into is that since these are customer instances, we don't have anyone on our team who has admin so getting email addresses in the user list updated is not something we can control.

Comment

Thomas Deiler is a Bavarian, Mountaineering, Senior Agile Coach. In this Showcase, you will learn about his journey from software engineer to project manager, his freelance philosophy, and much more....