Configure Jira host and project mapping for a Test Management project

Restrict which Jira hosts and projects testers can link to from a Test Management project, so issues never get created in the wrong client environment.

If your account connects to more than one Jira host, or if a single Jira host contains projects for several customers or teams, Test Management lets you scope Jira destinations to each Test Management project. Configure mapping once, and the issue creation and linking widget only shows the destinations you allow.

Before you begin

• Connect at least one Jira host to your BrowserStack account. See Jira integration with Test Management.
• Sign in to Test Management with a Project Admin or Project Creator role. Other roles can view the settings but cannot change them.

How Jira mapping works

Each Test Management project has its own Jira mapping. Mapping runs in one of two modes:

A Test Management project starts in Standard Mapping. Switch to Advanced Mapping when you want a narrower allowlist.

The two modes are independent of Jira host count. The Default Host for Quick Linking dropdown appears under both modes, but only when two or more Jira hosts are connected to your account.

Access Jira mapping settings

1. Sign in to Test Management.
2. From the left navigation, open the Test Management project you want to configure.
3. In the project sidebar, click Settings.
4. Under Project Settings, click Requirement & Defects.

The JIRA Settings card appears on the page. If no Jira host is connected to your account, the card shows a Connect with Jira button instead of the configuration options. Connect Jira first, then return to this page.

Configure Standard Mapping

Use Standard Mapping when every Jira host and project connected to your account is a valid destination for this Test Management project.

1. In the JIRA Settings card, click Standard Mapping.
2. If two or more Jira hosts are connected, choose a host from the Select Default Jira Host dropdown. This host is pre-selected in the issue widget when a tester uses Quick Linking to create a Jira issue. The tester can still switch hosts per link.
3. Click Save changes.

If only one Jira host is connected, the Default Host for Quick Linking section is hidden. The single connected host is the implicit default.

Configure Advanced Mapping

Use Advanced Mapping to allow only specific host and project combinations for this Test Management project.

1. In the JIRA Settings card, click Advanced Mapping.
2. In the JIRA Hosts panel on the left, click the host that contains the projects you want to allow.
3. In the Projects in ‘<host>‘ panel on the right, select the checkbox next to each Jira project you want to allow. To find a project in a long list, type its name into the Search projects by name field.
4. Repeat steps 2 and 3 for each additional Jira host you want to include. A host becomes active as soon as you select at least one project inside it. The host row then shows a Selected badge with the project count.
5. If two or more Jira hosts have projects selected, choose a host from the Select Default Jira Host dropdown. The default host applies when a tester uses Quick Linking and has access to that host. If the tester does not have access, the widget opens with no host pre-selected.
6. Click Save changes.

The mapping takes effect for new Jira actions inside this Test Management project as soon as the save completes.

How the Jira issue widget behaves after configuration

The widget that opens when a tester creates or links a Jira issue respects the project’s current mapping.

Testers cannot reach a Jira host or project that is not in the allowlist from inside this Test Management project, regardless of their Jira account permissions.

Behavior of existing Jira links when mapping changes

Changes to a project’s Jira mapping apply to new issue creation and linking only. Existing links are forward-compatible.

This applies to the following situations:

• A previously allowed Jira project is removed from the Advanced Mapping allowlist.
• A Jira host is disconnected at the account level.
• A Jira project the user once had access to becomes inaccessible from the Jira side.

In each case, existing linked issues remain on the Test Case or Test Run record. New issue creation or linking against the affected destination is blocked from this Test Management project going forward.

Known limitations

• Mapping changes do not retroactively migrate or remap existing Jira links. Plan host or project changes alongside any data clean-up your team needs.
• Cloning or moving a test case or test run between Test Management projects keeps the original Jira links. New linking actions in the destination project follow the destination project’s mapping.
• If the default host loses access at the Jira side, the Default Host dropdown shows the host as invalid. A Project Admin must reconfigure the default before testers can use quick linking again.
• Audit log entries for mapping changes are not yet available. Track configuration history through your own change management process until audit logging ships.

Next steps

• Set up two-way binding between Jira and Test Management
• Manage test cases in Jira with Test Management
• Manage test runs and tracking results in Jira