Migrate
Move from Cucumber for Jira
Your feature files already live in Git, so moving is mostly connecting the same repository. FeatureBridge then shows them on their Jira issues, lets you edit them there, and adds CI results.
What changes
| Cucumber for Jira | FeatureBridge |
|---|---|
| Feature files in your Git repository | The same files, linked to issues and kept in two-way sync: saves in Jira commit, pushes update the issue. |
| Living documentation in Jira | The Scenarios panel on each issue and the project's Scenarios page. |
| Git hosts | GitHub, GitLab (gitlab.com) and Bitbucket Cloud. Self-hosted Git servers are not supported yet. |
| Test results | Upload the Cucumber JSON report from CI to see ✓ / ✗ per scenario. |
1. Make sure files point to their issues
FeatureBridge links a file to an issue by:
- an issue-key tag on the feature, such as
@SHOP-12, or - the issue key in the file name, such as
SHOP-12-checkout.feature.
If your files use neither, add a key tag to each feature (one line, commit and push), or use the .feature file import, which can also match an issue with exactly the feature's name.
2. Connect the same repository
Install FeatureBridge and turn on Show for all work items for the Scenarios panel (see Install and set up).
Open Jira settings → Apps → FeatureBridge and connect the repository, branch and folder Cucumber for Jira uses.
Click Import from the repository.
Every
.featurefile with a key appears on its issue. Files in Git are not changed by the import.
If Cucumber for Jira also writes to Git
Stop editing in Cucumber for Jira once FeatureBridge is connected, so only one app commits changes.
3. Add CI results
Create an upload key in FeatureBridge and add one curl step after your tests. See Upload CI results for GitHub Actions and GitLab CI examples.
4. Check, then switch off Cucumber for Jira
- Open the project's Scenarios page and compare the list with your repository.
- Edit one scenario in Jira and check the commit in Git, then push a change and check the issue.
- When everything matches, uninstall Cucumber for Jira. Your files in Git are not affected.
Need a hand?
Email support@yti.digital. We help with migrations, including adding key tags to many files.
Cucumber for Jira is a product of its respective owner; FeatureBridge is not affiliated with it. Self-hosted GitLab or Bitbucket Server users: tell us, it helps us prioritise.