This is still an issue. The problem is that there is no method to remove this for a managed user under Access. A Bitbucket user can delete all the workspaces they own or are members of, but they still show up in Access as having access to Bitbucket cloud product. As a managed user however, they are not able to delete their Bitbucket account, which is what is required (apparently there is a shadow account record within Bitbucket cloud which is different than with jira/confluence which seem to rely directly on the Access level Atlassian account.)
I worked with a support person on BBS-202310 and that ticket will demonstrate than when the support person removed the Bitbucket cloud copy of a user account then project usage no longer showed on the Access listing.
So, the problem here is there is no method for a user or Access admin to do the same here once the account is managed. And if you are using provisioned users and SCIM, there is no method to unmanage users to enable the removal of the Bitbucket account. And at scale of starting to implement access when not previously used, it can be tedious to have to address hundreds of users in this situation (in our case, we purchased a company that had been using Bitbucket cloud and later moved the repos to Bitbucket data center which left hundreds of accounts in Bitbucket cloud which were no longer active product users; however they appeared to be when we began to implement Access a few years later)
Please reopen and revisit this issue. In general, consolidating this account management for Bitbucket to work the same way as JIRA/Confluence would really be the proper answer, but I'll take something that addresses this part of the issue at a minimum
This is still an issue. The problem is that there is no method to remove this for a managed user under Access. A Bitbucket user can delete all the workspaces they own or are members of, but they still show up in Access as having access to Bitbucket cloud product. As a managed user however, they are not able to delete their Bitbucket account, which is what is required (apparently there is a shadow account record within Bitbucket cloud which is different than with jira/confluence which seem to rely directly on the Access level Atlassian account.)
I worked with a support person on BBS-202310 and that ticket will demonstrate than when the support person removed the Bitbucket cloud copy of a user account then project usage no longer showed on the Access listing.
So, the problem here is there is no method for a user or Access admin to do the same here once the account is managed. And if you are using provisioned users and SCIM, there is no method to unmanage users to enable the removal of the Bitbucket account. And at scale of starting to implement access when not previously used, it can be tedious to have to address hundreds of users in this situation (in our case, we purchased a company that had been using Bitbucket cloud and later moved the repos to Bitbucket data center which left hundreds of accounts in Bitbucket cloud which were no longer active product users; however they appeared to be when we began to implement Access a few years later)
Please reopen and revisit this issue. In general, consolidating this account management for Bitbucket to work the same way as JIRA/Confluence would really be the proper answer, but I'll take something that addresses this part of the issue at a minimum