You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Sorry to hear about this problem, this does appear to be a bug. We have a ticket about this issue that you can see in CLOUD-10963. Please vote on that issue if you're affected by this problem.
Should a workaround become available or a fix be applied to Atlassian Cloud sites about this, I would expect that ticket to be updated to reflect this.
Generally, if you continue to navigate to new screens it will reappear if in fact you are truly still logged in as the other user. This can be assessed by looking at the avatar/profile in top right.
I just had a ittle different issue, I have ompersonated an user and got stuck as the user, no "swtich back" pop up. Logging out did not help, but then I've found this workaround:
A manual workaround is to have the admin to navigate to <siteurl>/impersonate, which will reset the impersonate function. e.g. acme.atlassian.net/impersonate
I was able to work around this, and eliminate the annoying message. The problem started when I logged in as an impersonation account. Instead of switching back, I logged out of the impersonation account and then logged back in with my native account. After doing that I received the annoying pop up every time I accessed the application.
So I used the following corrective process: I logged in again as the same impersonation account and then 'switched back'. This seems to be key because this corrected the problem. I no longer receive the annoying message when I log into the application.
Atlassian: You need to fix the logout function for an impersonation account to clear out whatever application state is cleared out by the 'switch back' function.
@Daniela Griesinger , I would recommend reaching out to Atlassian Support given the original issue has been marked as resolved. This will allow them to log into you instance, with your permission, and have a look.
It wouldn't do any good for me to see as I'm but a user like yourself. This is something Atlassian would need to explore.