Bitbucket

The Arcus Bitbucket integration sends every pull request your team raises to QI Home, where Arcus generates test cases from its code changes.

Prerequisites

An active Arcus project.
Admin access to the Bitbucket workspace.

Connect Bitbucket

Developers don’t change how they work. Once Bitbucket is connected, every pull request reaches Arcus on its own.

In the left navigation, go to Settings > Integrations, and click Connect next to Bitbucket.
Sign in to Bitbucket if prompted, and select the Bitbucket workspace to connect.
Select all repositories, or choose specific repositories.
Click Grant access. Bitbucket redirects you to Arcus.
In the Connect Bitbucket dialog, select the Workspace and Project to link this connection to.
Click Connect.

Pull requests raised in the connected repositories now arrive on the Unlinked Contexts tab of Context Management.

Map pull requests automatically

With a tracker such as Jira connected, a pull request whose title or description contains a ticket ID such as PROJ-123 goes straight to the sprint holding that story. It never reaches Unlinked Contexts, and nobody maps it manually.

Verify the connection

In the left navigation, go to Settings > Integrations.
Under Bitbucket, confirm the workspace name and repository list appear with a Connected status.
Raise a test pull request in one of the connected repositories.
Open QI Home > Context Management. The pull request appears on the Unlinked Contexts tab within a few seconds.

Map a pull request

On Unlinked Contexts, click Map to Module on the pull request, then pick a sprint and its stories, or an Adhoc session. Arcus generates test cases from the pull request’s changes, and the entry moves to Linked Contexts.

The full steps, including mapping several entries at once and discarding one that isn’t relevant, are in Context Management.

Was this page helpful?