Extremely frustrating. Atlassian hides menu items if we don't have permissions, so I can't count how many times devs are stumped by a missing functionality that was described so clearly as an easy win in the Atlassian documentation but turned out to be stymied by the way someone set up the workspace. Who cares if Ben created it as a personal workspace a billion years ago, and then we have been using it ever since? Apparently Atlassian, because we cannot create an Oauth Consumer. We haven't been told that we can't have Apps or Features... Google `atlassian "apps and features"` and you find that the main result is many many customers cannot actually access apps or features. What!? Really!?

768ab86f633d Yes, it's very frustrating and I, too, am very surprised it hasn't been fixed in 4 years.

In our case, as I mentioned, one of our non-owner Bitbucket users had been able to set up OAuth consumers in the workspace for several years but then became unable to do so recently. If the user is to be able to continue generating OAuth consumers, the only workaround I've found would be to create a new workspace and move the repository there, but that would present a considerable hassle for us and our existing customers:

• We would need to generate all new OAuth credentials for all of our existing customers since we're no longer able to access the ones previously created using that account.
• In order to continue receiving updates, all of our existing customers would need to update the repository URL(s) as well as their OAuth credentials in composer.
• For tracking purposes, our customers' license keys match our customers' OAuth keys, so, to keep the same system in place, all of our existing customers would either need to be given a new license key matching their OAuth key (which they would need to update in the software for validation purposes) or we would need to accept that existing customers' license keys would no longer match their new OAuth keys. Obviously not ideal but we could live with it.
• We would need to update the repo URL(s) in packagist, Gitlab, etc.

The way I understand it those are the issues we would face with the "workaround" mentioned here.

4574acb939a8 

I'm quite surprised this issue still hasn't been resolved.

The issue I encountered was when creating a new workspace, only the original owner has access to the "Apps & Features" section, while other invited owners cannot view or use it. This limitation makes managing and migrating Bitbucket difficult. We eventually had to assign a DevOps team member to handle requests from various owners through the creator's account, which was frustrating and inefficient.

In our case, all of our users – for the last 3-4 years – have had access to the APPS AND FEATURES section in the "personal" workspace up until just recently. We know this because they've been successfully generating OAuth consumers! Now, all of a sudden, the APPS AND FEATURES section is gone so they're no longer able to create new OAuth consumers – or even see the ones they previously created.

What changed recently that is now preventing us from doing what was previously possible? Why had it been possible if this ticket is 4 years old and still open??

So many questions...with a heavy dose of frustration.

No this isnt fixed. We're facing the same issue.

Has this been fixed? Any update? 

has this been fixed? I am currently facing the same issue.

https://getsupport.atlassian.com/browse/BBS-180681