Skip to content

Commit d8fd87f

Browse files
claudiacodacyclaude
andcommitted
docs: explain the Atlassian permissions prompt at Bitbucket login [OD-989]
Atlassian now shows its permissions page on every authorization for Bitbucket OAuth apps, so Bitbucket users see it at every Codacy login. Add it to the Bitbucket Cloud limitations so support and the app have a page to point to. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent bf04941 commit d8fd87f

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎docs/faq/general/how-does-codacy-support-bitbucket-cloud.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ Currently, the integration between Codacy and Bitbucket Cloud has the following
1919
- **Repositories that are moved between teams are not automatically transferred between Organizations on Codacy.** You must manually delete these repositories from their source Organization and add them to their new Organization.
2020
- **Codacy only sends commit and pull request notification emails to the authors of the commits and pull requests.**
2121
- **Codacy doesn't analyze pull requests submitted from forked repositories.**
22+
- **Atlassian asks you to grant Codacy access every time you log in to Codacy with Bitbucket.** Atlassian now shows its permissions page on every authorization, even if you granted access before, and Codacy can't turn it off. The permissions are the same each time, so you can accept them to continue. See [which permissions Codacy needs](../../getting-started/which-permissions-does-codacy-need-from-my-account.md#bitbucket-cloud).
2223

2324
## See also
2425

0 commit comments

Comments
 (0)