"There was a problem fetching the organization name"

[Michael Karl]

Hi. We're on Standard plan with our organization at mhndigital.atlassian.net and we migrated to the cloud two years ago.

Today, I got the error message "Uu oh! Something went wrong. There was a problem fetching the organization name." for the first time. It came up after getting to the user administration at https://admin.atlassian.com/ from Jira Software using the cogwheel-icon-menu.

A short query uncovered a known (and already closed) issue from 2023 and an even older (2021) question in this community. Trying to get rid of the error by closing VPN-connections, deleting cookies or trying an incognito browser tab didn't help.

Do you have any suggestions how to solve the problem which seems to be reoccuring in the user community once in a while?

Any help is very appreciated.

Michael Karl

[Sami Shaik]

Hi @Michael Karl ,

Thanks for reaching out — and I understand how frustrating this kind of error can be, especially when it blocks access to user administration.

Here's what you can try:
Verify Org Association
Go to https://admin.atlassian.com/o directly and see if you're able to select your organization. Sometimes the redirection from the cogwheel can glitch if there's a session token issue or an expired cookie.

Check Product Access & Role
Make sure you're still an Org Admin for your Atlassian organization. If your permissions changed or if the user session is out of sync, the admin console might fail to fetch data.

Force Clear Session & Login Again

• Log out from all Atlassian products
• Go to https://id.atlassian.com/logout to force session termination
• Then re-login fresh from admin.atlassian.com

Check for Browser Extensions / Script Blockers
Tools like uBlock Origin, AdBlock, or privacy extensions (e.g. DuckDuckGo, Ghostery) sometimes interfere with Atlassian Admin Console rendering.

Known Past Incident
Yes, you're right, this error was previously tracked under a resolved Atlassian incident (and a similar community thread in 2021). While the backend issue was fixed, it could recur intermittently due to session or DNS propagation issues.

If the issue persists:

Raise a ticket with Atlassian Support here: https://support.atlassian.com/contact  

Provide the error message, affected URL, and your browser's dev console screenshot (if possible)

Since you're on the Standard plan, you're eligible for support — and Atlassian can review backend logs to help troubleshoot.

Let us know how it goes!

Best regards,
Sami.

[Michael Karl]

Hi @Sami Shaik 

Thanks for getting back to my request. First of all, I never was org-admin, I'm just Site-Admin. 

But that used to be sufficient to invite new users at https://admin.atlassian.com/s/b910d383-9dd8-4b58-9a36-99e9bb7adf8c/users?referrerName=JIRA and give them access to Jira and our project. But today I witnessed to error for the first time.

I tried all your suggestions and had some home that the forced logout might help, but the problem is still persistent.

So I'm going to move on and raise a ticket as you suggested.

Best regards,

Michael