QA TOUCH + BITBUCKET

Bugs from QA Touch, on your Bitbucket Issues tab

Map a Bitbucket repository to each QA Touch project, and bugs your testers post are created in the repository’s issue tracker, where developers already look.

Setup: Bitbucket credential, issue tracker, repository mapping

QA Touch finds the bug. Bitbucket holds the issue.

Connect Bitbucket to QA Touch once, then map repositories to your QA Touch projects. Bugs found during testing go straight to the issue tracker of the repository where the code lives.

  • Problem: A bug found in testing has to be re-typed as a Bitbucket issue.

    With the integration: Bugs posted in a mapped QA Touch project are redirected to the Bitbucket Issues tab.

  • Problem: Each project’s code lives in a different repository.

    With the integration: Mapping is per project, so each QA Touch project posts to its own Bitbucket repository.

  • Problem: It’s unclear who can see the bugs once they are posted.

    With the integration: Visibility follows the repository’s issue tracker setting: private to repository users, or public.

Illustrative sample data. The page shows the idea of the posting, not the exact fields QA Touch sends.

What the integration does

Four capabilities from QA Touch’s Bitbucket guide and blog post, from the first connection to the bug on the Issues tab.

Connect once for the account

An Administrator connects Bitbucket under Administration → Integration Settings → Bitbucket. The status shows connected.

Administrator setup

Map a repository to a project

Open Projects → Project mapping, select a Bitbucket repository and submit it for the QA Touch project.

Per-project mapping

Bugs go to the Issues tab

After a successful integration, bugs posted in the mapped QA Touch project are redirected to the repository’s Issues tab.

Visibility you control

Enable the Issue Tracker per repository. A private tracker follows repository access; a public one lets anyone view, create and comment.

From Bitbucket credential to bug on the Issues tab

Step through the flow. The screens are schematic, drawn from the labels in the setup guide, not screenshots.

One-time Bitbucket settings Access management

Create the Bitbucket credential

QA Touch's guide has you create a named credential in Bitbucket, choose its permissions and copy it, because Bitbucket shows it only once.

Bitbucket Repository Settings

Enable the Issue Tracker

In each repository you want to post to, open Settings in the left navigation and enable the Issue Tracker.

QA Touch Administrator Administration → Integration Settings → Bitbucket

Connect Bitbucket in QA Touch

An Administrator enters the credential from the guide and clicks Update. The status shows connected.

QA Touch Projects → Project mapping

Map a repository to the project

Select a Bitbucket repository and click submit to map it to the QA Touch project.

QA Touch Bitbucket Issues tab

The bug appears on the Issues tab

Bugs posted in the mapped QA Touch project are redirected to the repository's Issues tab.

Illustrative sample data. Repository and bug names are examples.

What changes for your QA team

Testing stays in QA Touch. What it finds shows up next to the code.

No double entry

Testers raise the bug once in QA Touch. It is redirected to Bitbucket instead of being typed in again.

Bugs sit with the right code

Each QA Touch project maps to a repository, so its bugs land in the issue tracker of the code they concern.

Testers and developers share a tracker

Developers pick up bugs from the Issues tab of the repository they already work in.

One setup for the whole account

An Administrator connects Bitbucket once. After that, each project only needs a repository mapping.

Who uses it, and for what

Choose a role to see a scenario the integration supports.

A team keeps its code in Bitbucket

The team already tracks issues in Bitbucket and wants QA Touch connected before testing starts.

What they do

  1. Create the Bitbucket credential and enable the Issue Tracker in each repository.
  2. Connect Bitbucket under Administration → Integration Settings → Bitbucket.
  3. Map a repository to each QA Touch project.

Result: the account is connected and each project has a repository to post to.

A checkout test fails

You are testing in a mapped project and find a bug that developers need to see.

What they do

  1. Post the bug from the mapped QA Touch project.
  2. Add the details in QA Touch.
  3. Carry on testing.

Result: the bug is redirected to the repository's Issues tab in Bitbucket.

Several products, several repositories

Each product's code lives in its own repository.

What they do

  1. Open Projects → Project mapping for each QA Touch project.
  2. Select the repository that product uses.
  3. Click submit.

Result: each project's bugs go to its own repository's issue tracker.

You work from the repository

You want QA findings next to the code you are changing.

What they do

  1. Open the Issues tab of your repository.
  2. Find the bugs posted from QA Touch.
  3. Work them like your other issues.

Result: QA findings arrive in Bitbucket without anyone copying them over.

Set it up in three parts

These steps follow QA Touch’s Bitbucket integration guide: first in Bitbucket, then in QA Touch, then per project.

Before you start

  • A Bitbucket account with access to the repository you want to post to.
  • The Issue Tracker enabled in that repository.
  • A QA Touch Administrator login for the global configuration.

The guide uses a Bitbucket app password. Atlassian stopped allowing new app passwords on 9 September 2025 and retired existing ones on 9 June 2026, replacing them with API tokens. Check QA Touch’s setup guide (opens in a new tab) for the current credential steps, and see Atlassian’s notice (opens in a new tab).

  1. Click your avatar in the bottom-left corner and open Bitbucket settings.
  2. Under Access management, open App passwords and click Create app password. This is the step Atlassian has retired; see the note under “Before you start”.
  3. Name it for QA Touch and choose its permissions. The guide lists Read and Write for Account (including Email), Pull requests, Issues, Projects, Snippets, Repositories and Webhooks.
  4. Copy the value. Bitbucket shows it only once.
  5. In each repository, open Settings in the left navigation and enable the Issue Tracker.
  1. Log in to QA Touch as an Administrator.
  2. Go to Administration → Integration Settings → Bitbucket.
  3. Enter the app password.
  4. Click Update.

connectedThe status shows connected when the configuration succeeds.

  1. Go to Projects → Project mapping.
  2. Select a Bitbucket repository and click submit to map it.
  3. Bugs posted in the mapped QA Touch project are now redirected to the repository's Issues tab.

Repository mapped? See how a bug reaches Bitbucket.

Questions about the Bitbucket integration

Answers are based on QA Touch’s Bitbucket integration guide and blog post.

What does the QA Touch Bitbucket integration do?

It connects QA Touch to Bitbucket. Once a Bitbucket repository is mapped to a QA Touch project, bugs posted in that project are redirected to the repository’s Issues tab.

As an Administrator, go to Administration → Integration Settings → Bitbucket, enter the Bitbucket credential from the guide and click Update. The status should show connected. Then map repositories under Projects → Project mapping.

Atlassian stopped allowing new Bitbucket Cloud app passwords on 9 September 2025 and retired existing ones on 9 June 2026, replacing them with API tokens. QA Touch’s guide describes the app password, so check it for the current credential steps before you set up.

Yes. Enable the Issue Tracker in each repository you want to post to, using Settings in the repository’s left navigation.

It depends on the repository’s issue tracker. With a private tracker, a user’s access to the code repository also applies to the tracker. With a public tracker, anyone can view, create and comment on issues, even without access to the code.

Go to Projects → Project mapping, select a Bitbucket repository and click submit.

The guide and blog post describe bugs going from QA Touch to Bitbucket. They don’t describe changes syncing back or which bug fields are sent.

Connect Bitbucket to QA Touch

Connect once, map a repository to your first QA Touch project, and let the next bug reach the Issues tab on its own.