-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
Problem
The Domains page takes too long to completely load when there are hundreds of domains claimed.
Current Behaviour
When you first access the Domains page,
- It first loads the list domains which takes about ~250ms to load
https://admin.atlassian.com/gateway/api/adminhub/organization/<orgID>/domainClaims - Then there are 3 calls per domain triggered to lazy load the memberTotal, count and fetch data
GET https://admin.atlassian.com/gateway/api/adminhub/organization/<orgID>/domainClaims/<domain.name>/memberTotal GET https://admin.atlassian.com/gateway/api/admin/private/api/admin/v1/orgs/<orgID>/domains/<domain.name>/managed-accounts/count POST https://admin.atlassian.com/gateway/api/admin/private/api/admin/v1/orgs/<orgID>/managed-accounts/config/fetch
By the time the calls are all completed, and the page is fully populated, it'll have taken about 40s (for an org with 445 domains claimed) mark.
This becomes a problem for Enterprise organizations that need to claim thousands of domains
Suggested Solution
Improve the way the Domains page loads the valuable data (All/Managed/New accounts). Ideally, some sort of pagination for the response.
Why This Is Important
While the initial page load shows the list of domains, the valuable data is in the All/Managed/New accounts section which only comes after lazy loading. So when there are thousands of domains claimed it'll take too long.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available.
- mentioned in
-
Page Failed to load
With ~ 3300 domains (which is ~ 75% of what we know we need to claim for our org), this page is completely unusable. Depending on the user/browser, the page will either be blank with no errors (assume due to the huge amount of AJAX requests/DOM requests happening), or, if the domain list does load, the UI will start throwing errors for each domain "Something went wrong: please try later"
Assuming this is due to a REST API rate limit being hit.
As this page does not load, we are unable to:
This means we are unable to continue to secure our Atlassian Cloud footprint in our enterprise, which is the entire point of this product.
This ticket should NOT be a suggestion. This is a critical Bug as defined by your own policy https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html as all three of the below requirements are true.
CCM