Workspace rename stuck 48+ hours after recent account username change (Slug unavailable / 404)

[Shimon Rothschild]

I initiated a workspace rename from <OLD_WORKSPACE_SLUG> to <NEW_WORKSPACE_SLUG> about two days ago. The rename has not completed, and I'm seeing inconsistent behavior across the UI and API:

• Current status: The workspace still displays the old slug everywhere (browser URLs, API responses, clone URLs).

• Retry attempt: Attempting the rename again reports the target slug (<NEW_WORKSPACE_SLUG>) as "not available".

• Direct URL: Navigating directly to bitbucket.org/<NEW_WORKSPACE_SLUG>/ yields a 404 error.

• Workspace Switcher: The new workspace slug does not appear in my workspace switcher.

• UI Pickers: However, <NEW_WORKSPACE_SLUG> does show up as a selectable option in certain UI dropdown pickers (e.g., when selecting a workspace context while creating a community post). It seems to exist at some internal database level, but isn't accessible or usable anywhere.

Additional Context: Shortly before initiating this workspace rename, I changed my personal account username from <NEW_WORKSPACE_SLUG> to a new name to free up that specific handle for the workspace.

It seems possible that changing the personal handle left a stale reservation or orphaned record tied to the original account handle that is now blocking the workspace rename job from finalizing.

Since this has been stuck for 48+ hours, is this a known backend job deadlock, and can an Atlassian admin help clear the reservation lock?

(Note: Happy to provide original workspace IDs and actual usernames privately to support staff if needed.)