Workspace provisioning is still incomplete after 12 days — users remain invited

[vovavovk]

Hello,

I am creating a new post because my previous topic has not received any further response, and the issue is still unresolved.

Previous topic:
https://community.atlassian.com/forums/Bitbucket-questions/Workspace-setup-in-progress-for-more-than-3-days/qaq-p/3261091

Workspace ID: vitryna
Workspace URL: https://bitbucket.org/vitryna/

The workspace setup banner has remained visible for 12 days:

“Workspace setup in progress. Groups and users may not be fully available for multiple hours. This banner will disappear once the process completes, upon page refresh.”

The repository has already been transferred successfully to this workspace.

However, there are still functional issues:

- invited users remain in the “Invited” status;
- accepting the invitation does not activate their access;
- users are redirected to the Atlassian home page;
- workspace groups and permissions do not appear to be fully provisioned;
- even my personal account, which is the owner and administrator of the workspace, is still shown as “Invited” and has not been fully activated.

I have already tried:

- clearing browser cache and cookies;
- signing out and signing in again;
- using another browser;
- using an incognito/private window;
- resending invitations.

This is not only a visual banner issue. User and group provisioning appears to be incomplete.

Could an Atlassian team member please check the backend provisioning status for workspace “vitryna” and escalate this issue to the Bitbucket Cloud team?

It seems that the workspace migration or unified user management setup may be marked as completed, while user and group synchronization is still stuck.

Thank you.

[Tomislav Tobijas]

Hey @vovavovk ,

Could you maybe start a free trial of Standard or Premium plan and then create a ticket at Atlassian Support? Like, that's the fastest way you'll get official support member to help out and take a look at it 👀

I know it's not ideal, but as it would appear to be a backend issue, it's usually the fastest way to get things resolved.

Cheers,
Tobi

[vovavovk]

Thanks for the advice!