Bugbot PR review: Atlassian (Rovo) MCP shows Connected but Jira issue is not loaded — serverGenReqId attached

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Atlassian MCP is configured for Bugbot (team MCP server, API token auth). The Bugbot dashboard shows Atlassian as Connected. On PR review, Bugbot still behaves as if Jira data were unavailable (e.g. “Jira could not be loaded; scope inferred from PR title”), even when the PR title contains a valid issue key (e.g. JP-33378) and the same integration works in principle from our side.

Actual behavior
Bugbot infers scope from the PR title (fallback) and reports that Jira could not be loaded, despite MCP being Connected and configured with a valid API token.

Diagnostics / IDs:
serverGenReqId_a94851cd-6de5-4b40-ae00-19644863d4dc

Steps to Reproduce

Environment
Bugbot on GitHub PRs
Team MCP: Atlassian (Atlassian Rovo MCP Server–style remote MCP)
Auth: API token (org allows token auth for Rovo MCP)
Jira: Atlassian Cloud, issue key format e.g. JP-33378
Steps we’ve tried
Confirmed Bugbot → MCP Tools → Atlassian = Connected
Confirmed API token path (not relying on OAuth domain flow for this setup)
Custom review rules in .cursor/BUGBOT.md explicitly ask Bugbot to fetch the issue by key before comparing scope

Expected Behavior

When Bugbot runs on a PR whose title references a Jira issue key, Bugbot should successfully call the Atlassian MCP tools (e.g. fetch issue by key) and use summary / description / acceptance criteria in the review, assuming the token has access to that issue.

Operating System

MacOS

Version Information

We’re using latest BugBot

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @sambros!

This issue can occur when the PR author’s GitHub account isn’t linked to a Cursor account under https://cursor.com/dashboard/integrations. This is a known bug that we’re working to fix.

Could you confirm whether this is the case? If so, please try linking the GitHub account to a Cursor account (or creating a PR with a Cursor-linked GitHub account) and let us know if that resolves the issue.

7

Hey @Colin,

thanks for your reply.

Yes, it was linked to another account, but I linked now with the account, that is also doing the PR, sadly with the same result.

8

Hey @sambros!

For the paid user on your team, I don’t see any integrations with SCM providers (e.g., GitHub). Are you sure that you connected the account to the user who is running Bugbot?

9

Hi @Colin ,

What do you mean with “Paid” Member? The User “motammi” got a BugBot License and is associated with my Account, which is unpaid admin.

Do we have to have Cursor License for all Accounts + BugBot Licenses for all of them?

That would not make much sense to double pay just to use MCP in a PR.

10

Hey @sambros

Looked into it further and TIL that an Unpaid Admin can have a Bugbot license! Sorry about that (and glad I know now).

That said, we pushed some fixes on Friday for team-scoped MCP servers in Bugbot. I don’t see any new Bugbot runs for your team in quite some time. Could you try again, and bring back a new serverGenReqId if it’s still not working?

11

Hey @Colin ,

the issue still persists:

Here is the request id: serverGenReqId_27dd1738-52b0-486a-9590-1429eda299b2

Kind regards

12

Thanks @sambros. I was able to find some more logs for this run!

  • Is the behavior different when using OAuth instead of an API token?
  • Can you share exactly how you’ve configured the MCP server (tokens redacted, of course)!