Migrate

Import scenarios

Bring existing scenarios onto their Jira issues. You see a preview of every match before anything is saved.

First, show the panel on all issues

Imported scenarios appear only where the Scenarios panel is shown. Turn on Show for all work items first (see Install and set up).

From Behave Pro

Download all features of a Behave Pro project as a .zip:

Terminal

curl --fail -u USER:API_KEY \
  "https://behave.pro/rest/cucumber/1.0/project/PROJECT_ID/features?manual=true" \
  --output features.zip

USER, API_KEY and PROJECT_ID are in Behave Pro's project settings.

Open Jira settings → Apps → FeatureBridge and scroll to Import scenarios.
Enter the Jira project key and choose features.zip.
Check the preview, then click Import.

From .feature files

Same steps, but choose one or more .feature files instead of a .zip.

How files are matched to issues

In this order:

an issue-key tag on the feature, such as @SHOP-12;
the issue key in the file name, such as SHOP-12-checkout.feature;
an issue in the project whose summary is exactly the feature's name.

The preview

Status	Meaning
ready	Will be imported.
has scenarios already	Skipped, unless you tick Replace scenarios on issues that already have some.
no matching issue	Add a key tag or rename the file, then import again.
ambiguous	Several issues have this name. Add a key tag.
Gherkin error	The file is not valid Gherkin; the error is shown.
duplicate	Another file in the import goes to the same issue.

If a repository is connected, imported scenarios are committed to it as well. Up to 25 files are saved per batch; large imports continue automatically.

From the connected repository

Already keeping features in Git (for example after Cucumber for Jira)? Connect the repository, then click Import from the repository on the settings page. Files are matched by key tag or file name.