I do work for several different companies. Many of these companies use cloud hosted JIRA.
I have to login to each company's JIRA account using a different user account, because these companies have nothing to do with each other. This is expected.
So far so good, right?
Not so good - because cloud JIRA won't let me stay logged into more than one account at a time.
So every time I try to look at a JIRA issue, if the previously viewed JIRA issue belonged to a different company, then the attempt fails with "wrong account".
Then I have to "try a different account" which means logging out and logging back in. This turns an already kind-of slow JIRA web experience into a truly glacial one.
Why can't I be logged into multiple cloud hosted JIRA accounts at once? Like the way Google allows you to be logged into multiple Google accounts at once (which I depend on for the analgous capability with these customers).
A basic answer to this quesitons is because two separate Cloud instances have 2 different sets of users. There is more information in Can I manage two Atlassian Cloud subscriptions with the same email address? and Does Jira no longer allow multiple users with same email address?
Hopefully this helps.
I also have the same issue, but since this has been going on for so long, I am using a workaround until they figure out a way to fix it.
My preferred way is to use Chrome browser and open a second incognito window (ctrl+shift+n) and open the second instance of JIRA (or other Atlassian product) there. It will let you have them both logged in at the same time. I guess other browsers will have an equivalent.
The second option is to use 2 browsers. you get the same effect but you will not be using your favorite browser half the time.
I hope this helps.
Seems that my workaround was actually their officially suggested solution:
A user there suggests a Mozilla fix. I haven't tried it, but it seems interesting if that is your browser.
That's can't be a solution. The Instance running on a total different URL. Not even the Browser will send session infos (cookies) to the individual URLs.
Atlassian have made a major mistake in implementing either the Cloud Application or more likely the Account Management. I'm not aware of any other Cloud offering makes such mistakes across separate Cloud instance.
This really needs to be fixed.
For a very long time, google made the same mistake with its google accounts. It now allows you to swap between accounts and be logged in with more than one separately in some of its applications.
Atlassian simply don't expect most users to have more than one Atlassian account, because most people will simply not need to have more than one. Even I only have two - one associated with Adaptavist which has access to client Cloud sites and Atlassian partner resources, and this one here which has been around for a lot longer, and I need to keep if I ever left.
You are right, Google had similar difficulties long ago in the past.
However, it was slightly different as the services run for different accounts under the same domain. Even the branded domains are just redirects to the central one.
Google explains this with the arguments that they don't want to bother you with individual cert management.
This situation leads to a requirement of supporting this different users in the application self. We experience this with the "switch account" button top right in i.e. gmail.
With Atlassian Cloud is different, the make the impression of running your individual instances of Jira, Confluence etc. in the Cloud for you. Which leads already to different host parts of the URL like "mycompany.atlassian.net" I hope this individual Instance assumption is true, especially for GDPR reasons (but this would open another topic ;-)
Given different Instances with even different URLs I don't see the point why the HTTP Sessions, and thus authentications, are shared amongst individual instances just running in the Cloud. For me the problem don't even has something to do with UserIds here, it is a session problem not a user problem.
As the users are managed in a IdM at Atlassian, which is totally valid, it's seems either the case that the Account management System Authenticating the users mixes something up here, or more likely the session Logic of the Hosted instances makes this mistakes. Usually a IdM approves the User but does it make Session management of the individual, usually not even known, Service Implementation?
Long story short... Seems a HTTP session mess, whats going on here.
A team mate just come with the idea of changing the URL do a own TLD and give it a try. anybody knows Atlassian Cloud Services can run (not redirect) on customer provided TLDs? If yes, Anybody experienced the same problem across Cloud Instances on different TLDs?
OK, answered the question my self. Even running Jira on own domain in the Cloud is not supported.
As I can't believe that in 2018 where nearly everybody has this feature for paid services, I'll go to double check.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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