Hi @심제범 _jbsim0413_
Welcome to the Atlassian community!
This is not something you caused. It’s a known bug on Atlassian's side from the same day you posted. The official connector began requesting new scopes (write:goal:townsquare, read:goal:townsquare, write:project:townsquare, read:project:townsquare) that weren’t yet declared on its registered app, so Atlassian's authentication server blocked the consent. The tracking issue is now closed: https://github.com/atlassian/atlassian-mcp-server/issues/199
The fix on your side is to fully remove the Atlassian connector in your client, then reconnect so the OAuth consent runs fresh. A plain retry often reuses the old cached consent and keeps failing.
Does a clean disconnect and reconnect clear it for you?
Cheers, Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.