BitBucket / Cursor user mapping not working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

I recently installed the Cursor app into BitBucket. When I attempted to initiate a review of a PR in BitBucket I got the repsonse: ```

Bugbot couldn’t run

Bugbot is not enabled for your user on this team.

Ask your team administrator to increase your team’s hard limit for Bugbot seats or add you to the allowlist in the Cursor dashboard.```

I am an admin in both Cursor and in BitBucket. Bugbot is only enabled for my account. I suspect this may be because my username in both systems do not match (GitHub is a username, Cursor and BitBucket are email address based).

Steps to Reproduce

Go to an active PR in BitBucket and enter the comment cursor review verbose=true

Expected Behavior

Cursor Bugbot is able to translate between GitHub user account name and BitBucket user account name.

Operating System

Windows 10/11

Version Information

Cursor App for BitBucket version unknown

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey there!

For Bitbucket PRs, Bugbot’s Restrict Access allowlist matches the PR author’s Bitbucket username (the @nickname from their Bitbucket profile). It doesn’t match email addresses or GitHub usernames, so an email entry won’t match, which triggers “Bugbot is not enabled for your user on this team.” (Running cursor review manually doesn’t bypass this check.)

Two ways to fix it:

  1. Quickest: In the Cursor dashboard, open Bugbot settings and turn Restrict Access off. That removes the per-user restriction so Bugbot can run on your enabled repos.
  2. Keep it restricted: Replace the email with the exact Bitbucket username of each PR author (case-insensitive). The field is labeled “GitHub / GitLab username,” but Bitbucket usernames work there too. Make sure the PR author’s username is on the list, since that’s who Bugbot checks.

Docs: Bugbot. Let me know if either one unblocks you!

8

My BitBucket account is “managed” so the nickname for the account has a space in it (@ ). The input field does not allow for adding nicknames with spaces. What should I do?