Bitbucket

Pull requests and issues from the Bitbucket repositories you choose.

What Claro Historia reads

Pull requests
Issues

Access is read-only. Claro Historia does not create, change or delete anything in Bitbucket.

Permissions requested

repository:read, pullrequest:read and issue:read: read repositories, pull requests and issues.
account:read: identify the connected account.

Before you start

Bitbucket is connected once for the workspace, by an admin, through Atlassian sign-in. Claro Historia can only read repositories that account can already access.

Connect Bitbucket (workspace admin)

Open Workspace Settings → Sources.
Under Code & Repos, find Bitbucket and click Connect via Atlassian.
On the Bitbucket authorization page, click Grant access.
You return to Claro Historia and the card shows Connected.

Connecting Bitbucket from Workspace Settings.

Add Bitbucket repositories to a project

Open the project and go to Project Settings → Bitbucket.
Click + Add Repo and click a repository to link it.
Content syncs with the next run, or click Sync in Project Settings → Sync.

Adding Bitbucket repositories to a project.

Anything synced into a project can be seen by every member of your workspace, because every member can open every project. That includes people who cannot open the original file or message in the source tool. Only link sources you are comfortable sharing with your whole workspace.

Disconnect

For a project: click Remove next to a repository in Project Settings → Bitbucket.
For the workspace: in Workspace Settings → Sources, click Disconnect on the Bitbucket card.

Disconnecting stops syncing and removes Claro Historia’s access immediately. To have content that was already synced removed as well, email support@clarohistoria.com. See Data and security for how long data is kept.

Problems?

See Troubleshooting or email support@clarohistoria.com.