Troubleshooting

Quick fixes for the most common connection, AI and recording errors.

Jira says the credentials are invalid

Check that the token was created without scopes and that the email matches the Atlassian account that created the token. The URL must be your site's, such as https://yourcompany.atlassian.net.

GitHub lists the repositories but not the branches

The token does not have Contents: Read-only. Edit the token in GitHub, grant the permission and, if your organization requires it, ask the admin for approval.

Bitbucket rejects the token

The token must be created with Create API token with scopes, in the Bitbucket app, with read:repository:bitbucket. Also check the workspace and the email.

The AI analysis does not show up on the card

• Check that the analysis is turned on and the key is saved in AI Analysis.
• Check in AI Usage whether the monthly budget has been reached.
• An invalid key, or one with no credit at the provider, makes the analysis fail. Generate a new one and save it again.

Code analysis says it found no matching code

Check that the right repositories are selected, that the branch matches the environment where the bug happened, and that the repository is not limited to other boards.

The extension does not record

• Check that you are signed in to the extension.
• Reload the page after installing or updating the extension.
• If the account is suspended because of an overdue invoice, recording is paused until payment. See Billing.

Still stuck? Write to contato@capto.dev.