Issue trackers, wikis and code · Native connection

Bitbucket and TestingOps: pull requests and code as test context

TestingOps reads a Bitbucket Cloud repository's pull requests and README into its knowledge base and lets agents open its files, so test cases can follow what the code and its changes say. It does not write to Bitbucket.

Native connection
Available with limits

Request a demo Bitbucket Cloud: API tokens

Bitbucket Context TestingOpsAI test agents

Connection: Native connection
Writes back: Nothing, it only reads
Last checked: 7 Nov 2026

In short

Bitbucket and TestingOps in short

The Bitbucket connection links one Bitbucket Cloud repository to a TestingOps project. Its pull requests and README become context in the knowledge base, and agents can open files of the repository while they write cases.

If your team plans in Jira, the Jira Tester Agent looks for commits and branches in the repository that carry the Jira key and uses the files they changed in its impact analysis.

The connection is read-only: no comments, no issue filing and no agent rules on Bitbucket. Use Connect with Bitbucket, or your username or email with an API token or app password.

What it does

What it does for your testing

1
Pull requests become test context
Input
Open, merged and declined pull requests with title, description and state
TestingOps
Keeps up to 300 per sync as requirements in the knowledge base, most recently updated first, and the README as know-how
Output
Context for agents writing cases about recent changes
2
Jira keys in commits steer impact analysis
Input
Commits and branches whose message or name carries a Jira key
TestingOps
The Jira Tester Agent gathers the files those commits changed, plus the files of matching branches that still differ from the main branch
Output
Changed files that feed its choice of cases to run
3
The code answers a question
Input
An agent needs a validation rule or an error text
TestingOps
Lists folders and opens files of the repository through the Bitbucket API
Output
Cases based on what the code does, without cloning the repository

Step by step

How it works

ConnectUnder Integrations → Project tools, open Bitbucket and use Connect with Bitbucket, or enter your username or email and an API token or app password.
Link a repositoryIn Knowledge Base, add the repository (workspace/repo) under Code. Syncs run hourly and on Sync now.
Context and code for agentsPull requests and the README become knowledge; agents open files through the Bitbucket API when a task needs them.
Jira impactWith a Jira project linked to the same TestingOps project, the Tester Agent searches the repository for commits and branches that carry the item's key.

Bitbucket is read-only in TestingOps. Defects are filed to an issue tracker such as Jira.

Connect

Setup

In TestingOps, open Integrations → Project tools, select Bitbucket and choose Connect with Bitbucket, or enter your Username or email and an API token or app password.
Select Test connection, then Connect.
In Knowledge Base, pick the project, select + Add source under Code, choose the connection, pick the repository and select Link to RAG.

Documentation: Bitbucket Cloud: API tokens

Where you connect it in TestingOps: Integrations → Project tools → Issue trackers, wikis and code → Bitbucket

Use cases

Know what changed before testing

Trigger: A Jira item whose branch in Bitbucket carries its key reaches Test
Uses: Commits and branches with the key and the files they changed
Agent activity: The Jira Tester Agent adds the files to its impact analysis and runs the selected cases
Result: A Jira comment with the run result
Condition: Needs Jira events and the key in commit messages or branch names

Write cases from pull request descriptions

Trigger: A pull request with a detailed description is merged
Uses: The pull request text after the next sync
Agent activity: Agents find it in the knowledge search when they write cases for the feature
Result: Cases that reflect the described change
Condition: Up to 300 pull requests per sync

Check a rule in the code

Trigger: A tester asks an agent how a field is validated
Uses: Files of the linked repository
Agent activity: Opens the file that implements the rule and writes the steps from it
Result: Steps and expected results that match the code
Condition: Agents read one repository per project, the first one linked

Capabilities

Capabilities and limits

What is read

Pull requests (open, merged and declined) and, where a repository still has Bitbucket's legacy issue tracker, its issues: title, description, state and last update; up to 300 per sync
The README, as a know-how document
On demand for agents: folders and files of the repository, up to 200 KB per file, through the Bitbucket API
For the Jira Tester Agent: commits and branches that carry a Jira key, and the files they changed

What is produced

Requirements and a README document in the knowledge base
Changed files as input for Jira impact analysis

Where it can write

Nothing in Bitbucket: no comments, no issues and no pull request changes.

How it connects

Bitbucket Cloud: Connect with Bitbucket, or username or email with an API token or app password

Account and permissions

TestingOps reads with the permissions of the account or token
The form has no base URL field, so Bitbucket Server and Data Center connections cannot be created there

Limits

Read-only: no agent tracker tools, no defect filing and no Tester Agent rules
300 pull requests per sync; pull request comments are not read
Bitbucket Server and Data Center are not set up from the form
Agents read one repository per project

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team develops in Bitbucket Cloud and plans in Jira, and its branches are named like feature/SHOP-310-gift-wrap. When SHOP-310 moves to Test, the Tester Agent finds that branch in the linked repository and the files it changed against the main branch.

It adds those files to its impact analysis, runs the cases it selected on RunningOps and comments the counts on the Jira item. Nothing is written to Bitbucket.

Frequently asked questions

Can TestingOps comment on Bitbucket pull requests or file issues there?

No. The connection only reads. Defects go to an issue tracker such as Jira, and agent rules run on Jira, GitHub, GitLab or Azure DevOps items.

Does it support Bitbucket Server or Data Center?

Not from the connection form: it has no base URL field, so only Bitbucket Cloud can be set up there.

How does Bitbucket help impact analysis?

The Jira Tester Agent searches up to five linked repositories for commits from the last 90 days and branches that carry the Jira key, and uses the files they changed. The key must be in the commit message or the branch name.

Is my repository cloned?

No. Files are read one at a time through the Bitbucket API when an agent needs them.

API token or app password?

Either works in the API token or app password field, together with your username or email. Bitbucket describes API tokens as the long-term replacement for app passwords.

Next step

Using Bitbucket with Jira? Request a demo and bring an item whose branch carries its key.

Request a demo More project tools integrations