Skip to main content
Telara

Integrations / Bitbucket

Bitbucket logo

Bitbucket

Bitbucket code collaboration platform

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A Bitbucket Cloud workspace.
Admin on the workspace, or permission to install apps / create a token.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Bitbucket. Approve access in Atlassian if prompted.
2
Or create an app password
Some setups paste a Bitbucket app password. Create it under Personal settings → App passwords, then paste it in Telara.

Permissions Telara requests

  • repository
    OAuth 2.0
  • repository:write
    OAuth 2.0
  • repository:admin
    OAuth 2.0
  • pullrequest
    OAuth 2.0
  • pullrequest:write
    OAuth 2.0
  • issue
    OAuth 2.0
  • issue:write
    OAuth 2.0
  • pipeline
    OAuth 2.0
  • pipeline:write
    OAuth 2.0
  • account
    OAuth 2.0
  • team
    OAuth 2.0
  • account:write
    OAuth 2.0
  • email
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Basic auth

Basic authentication with username and app password

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Username
  • Token
API token

Atlassian API token (ATATT3x format), used as Bearer token

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API token

Knowledge

What gets indexed

ResourceCoverage
RepositoriesPartial — not every record the vendor holds is synced
Pull requestsPartial — not every record the vendor holds is synced
CommitsPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
RepositoriesUp to 1 dayRemoved records disappear on the next full sync
Pull requestsUp to 1 hourRemoved records disappear on the next full sync
CommitsUp to 1 hourRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Repositories, Pull requests, Commits.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Workspace vs project access is easy to under-grant. An empty project list is usually Bitbucket permissions, not a Telara outage.
Bitbucket Server / Data Center needs the instance URL; Cloud credentials will not reach it.