Guide
How to choose a BDD app for Jira Cloud: nine questions
By Miftode Vasilica, maker of Gherkin Studio ·
Choosing a BDD app for Jira Cloud comes down to nine questions: what platform it runs on, where your scenarios are stored, how you get them out, how it syncs with Git, what it does when Jira and Git disagree, how test results arrive, what data leaves Atlassian, what it costs for your whole site, and who answers when something breaks. This page explains why each one matters and how to check the answer yourself. At the end we answer all nine for our own app, including what it does not do.
The admin's afternoon
A Jira admin gets a message from the QA lead: the team wants a BDD app, can she pick one by Friday. She opens the Atlassian Marketplace, searches "BDD", and gets a page of listings that all say collaboration, living documentation and seamless.
None of that helps her choose. What helps is a list of questions with answers she can verify in a trial, in an afternoon.
1. What platform does it run on?
Jira Cloud apps run on Forge, Atlassian's current platform, or on Connect, the older one. Connect reaches end of support on 31 January 2027 (Atlassian announcement).
How to check: after installing a trial, open Atlassian Administration → Connected apps. Atlassian puts a banner on apps that still use Connect (what admins see). No banner means Forge. Our Connect checklist explains each banner.
2. Where are the scenarios stored?
Either inside Atlassian, in the app's Forge storage, or on the vendor's own servers. Neither is wrong. You need to know which, because your security review will ask.
How to check: the Privacy & Security tab of the Marketplace listing, and the vendor's privacy policy.
3. Can you get everything out?
The day you leave an app, you want plain .feature files, with the Jira key on each scenario.
How to check: during the trial, write three scenarios and export them. Open the file. If the issue key is not in it, leaving will mean matching scenarios to stories by hand. See linking scenarios to issues.
4. How does Git sync work?
Ask which direction: Jira to Git, Git to Jira, or both. Ask which providers, and whether self-hosted Git is supported if you have it. Ask what permission the token needs. A token with access to one repository is a smaller risk than one with access to your whole organisation.
5. What happens when Jira and Git both changed?
This is the question that separates tools. The safe answer is that the sync stops and a person sees both versions. The risky answer is "the latest wins".
How to check: change the same scenario in Jira and in the repository, then sync. Watch what happens. More in keeping Jira and Git in sync.
6. How do test results reach the story?
Most teams want a report format their tools already write, usually Cucumber JSON, and a single step in the pipeline. Ask what the story shows when one scenario out of ten fails.
7. What leaves Atlassian, and when?
Git sync has to reach your Git provider. AI features send story text to a model provider. Ask for the full list, and ask whether AI is off until an admin turns it on.
8. What does it cost for your site?
Marketplace apps are priced on every user of your Jira site, not on the people who use the app. A team of 12 testers on a site of 400 users pays for 400.
How to check: use the price calculator on the Marketplace listing with your site's real user count. Compare at that number, not at the "from" price.
9. Who answers, and how fast?
Send the vendor a real question during the trial. Time the answer. That is the support you are buying.
Our answers, for Gherkin Studio
| Question | Gherkin Studio |
|---|---|
| Platform | Forge |
| Storage | Forge storage, on Atlassian's infrastructure |
| Export | One .feature file per story in your Git repository, named KEY-123.feature |
| Git | Two-way, on a button press. GitHub, GitLab.com, Bitbucket Cloud. Token for one repository |
| Both sides changed | Sync stops. Line-by-line comparison. You choose |
| Test results | Cucumber JSON, one curl step. A story fails if any scenario failed |
| Leaves Atlassian | Git sync, to the provider you connect. AI drafts, to Anthropic, only if an admin turns them on with your own key |
| Price | Free up to 10 users. Then from $2.00 per user per month, less per user above 100, before taxes. Full table |
| Support | One person, the maker. Answers within one business day, Monday to Friday, 09:00–18:00 Bucharest time |
What it does not do. No test plans, no manual test runs, no dashboards. No Jira Data Center. No self-hosted Git. If you need a full test-management suite, this is the wrong app.
Where it stands. Gherkin Studio is on the Atlassian Marketplace, approved by Atlassian. It imports .feature files exported from Behave Pro, Cucumber BDD for Jira or any Git repository (import guide).
Short answers
Is there a free BDD app for Jira Cloud?
Gherkin Studio is free for sites of up to 10 users. Above that, it starts with the 30-day free trial of the Atlassian Marketplace, like other paid cloud apps.
Do I have to change BDD apps before 31 January 2027?
Only if yours still runs on Connect and the vendor has no Forge version. The banner in Connected apps tells you.
Can I try two apps at once?
Yes. Trials are per app. Use a small project and the same three scenarios in each.
Where Gherkin Studio fits
If the nine answers above suit your team, install it from the Atlassian Marketplace. The first 30 days are free.