Connect Bitbucket Cloud

Agile Analytics connects to Bitbucket Cloud with your Atlassian account email and an API token with scopes. Bitbucket no longer accepts app passwords, so connections made with a Bitbucket username and app password stop working and need to be updated (see Update an existing connection).

1. Create an API token

1. Go to id.atlassian.com → Security and choose Create and manage API tokens.
2. Click Create API token with scopes. A plain API token without scopes does not work with Bitbucket.
3. Name and expiry: give the token a recognisable name, for example Agile Analytics, and choose the longest expiry, one year (the maximum Atlassian allows). Set a reminder to replace it before it expires: from the moment a token expires, Agile Analytics reads nothing new from Bitbucket until you enter a new one (see Update an existing connection).
4. Select app: choose Bitbucket.
5. Select scopes: select the scopes in the table below.
6. Review the token and click Create token. Copy the token right away: Atlassian shows it only once.

2. Add Bitbucket to Agile Analytics

1. Go to Agile Analytics → Settings → Git Providers.

2. Click Add provider and pick Bitbucket.

   

3. Fill in the Bitbucket card:

   • Name: any name for this connection.
   • Atlassian account email: the email address of the Atlassian account that created the token (not your Bitbucket username).
   • API token: the token from step 1.

4. Click Test. When the token works, the card lists the repositories it can reach under Projects. Then click Save.

   

3. Select repositories

Select the repositories Agile Analytics should follow, as described in Add repositories to Agile Analytics. A webhook is created on each one, so new pull requests, approvals, merges and pipeline results arrive as they happen.

4. Import the history

Webhooks only bring in what happens from now on. To fill the dashboards with your past work, click Import history on the Bitbucket card. It imports the pull requests of the selected repositories updated since 1 January of the current year and shows how many it imported. It is safe to run again, for example after selecting more repositories.

All set!

Update an existing connection

A connection made with a Bitbucket username and app password shows the warning Bitbucket no longer accepts app passwords. To fix it, create an API token (step 1), enter your Atlassian account email and the new token in the existing Bitbucket card, and click Update. Do the same when a token expires: the card then says since when Bitbucket refuses it. Until you do, only new pull requests still arrive, through the webhooks; AI attribution, commit activity, review statistics and deployment imports stop. After the update the first three catch up in the following nightly runs, and the selected repositories and their webhooks stay as they are. Deployments that ran while the token was expired are not imported afterwards.

Troubleshooting