Launch offer ~~Connect~~ Forge

Leaving a Connect app? Move now, pay later.

Atlassian Connect end of support is 31 January 2027. If your BDD app for Jira runs on Connect, now is the time to move to a Forge app. This offer is for you.

Install before 31 January 2027Free until 28 February 2027You start paying in March 2027.

Install after Connect closesFirst 3 months freeCounted from the day you install.

BDD for Jira · built on Atlassian Forge

Keep your BDD scenarios after Connect ends.

Write Gherkin scenarios inside each Jira story, keep .feature files in Git, and see which tests pass. Bring the scenarios you already have with you.

Get early access How import works

In final development. Not on the Atlassian Marketplace yet.

Import your existing .feature files
GitHub, GitLab.com, Bitbucket Cloud
Install before 31 January 2027: free until 28 February 2027

PROJ-12 · Scenarios

Try it: this editor runs in your browser. Press Format tables, type a new line starting with Given to see step suggestions, or break a line to see the error. It's a simplified version of the editor inside Jira.

Given

Your BDD app runs on Connect, and Connect is ending.

Atlassian Connect, the older platform many Jira BDD apps run on, reaches end of support on 31 January 2027. After that, Atlassian fixes only critical security problems in Connect, and Connect features can be removed with little notice.

If your BDD app still runs on Connect, your team needs a plan, in a year when budgets are already tight.

TodayYour scenarios live in a Connect app. Everything still works.
31 January 2027Connect reaches end of support.
After thatOnly critical security fixes. Connect features can be removed with little notice.

When

You move your scenarios in four steps.

Nothing changes in Jira until you press Import, and anything we can't match is listed, never dropped silently.

Export your feature files from your current app, or take them from your Git repository.
In Jira, open Apps → Gherkin Studio and upload the .feature files or the zip.
Check the preview: every scenario is matched to its story by its @KEY-123 tag, a # Jira: KEY-123 comment, or the file name. Stories that already have scenarios are skipped unless you choose otherwise.
Press Import. Anything we couldn't match is listed with the reason.

Import preview: PROJ-10 and PROJ-11 will get one scenario each, and nokey.feature is listed as not imported because it has no Jira issue key. — Screenshot from the app's test harness in Chromium, not from a live Jira site yet.

Read the full import guide →

Then

Your team keeps working in Jira.

Write scenarios in the story

A Gherkin editor in every Jira issue, with highlighting, step suggestions from your project, instant error checks in plain English, and one-click table formatting.

Click Line N on an error to jump there.
All Gherkin languages work, from # language: fr to Romanian.

Scenarios panel: a password reset feature with line 12 highlighted in red and the message: Unexpected text Oops not gherkin, expected a step, a table row, a tag, Examples, Scenario or Rule.

Step suggestion: after typing Given a us, the editor suggests the existing step a user ana@example.com, used once. — Screenshot from the app's test harness in Chromium, not from a live Jira site yet.

Two-way Git sync that never overwrites silently

One .feature file per story in GitHub, GitLab.com or Bitbucket Cloud. When Jira and Git both changed, you see both versions and choose.

Keep the Jira version, keep the Git version, or use the editor text.
Project admins connect the repository; the token stays in Forge secret storage.

Git conflict view: both Jira and Git changed since the last sync, nothing was overwritten. A line-by-line diff shows the Git line removed and the Jira line added, with buttons Keep Jira version, Keep Git version and Use the editor text. — Screenshot from the app's test harness in Chromium, not from a live Jira site yet.

Test results on the story

Your CI posts a Cucumber JSON report. Each story shows passing, failing or not run, with the failing step.

Works with any tool that writes Cucumber JSON.
Scenarios map to stories through @KEY-123 tags.

Test results on a story: 1 of 2 failing. Request link passed; Link expires after one hour failed at the step Then I see it, with the message expected 410, got 200. — Screenshot from the app's test harness in Chromium, not from a live Jira site yet.

AI drafts, only if you want them

Off by default. A Jira admin can switch it on with your organisation's own Anthropic API key. Drafts include the edge cases people forget, and you review them before they're added.

Off by default

When someone clicks AI draft, the story's key, summary, description, existing scenarios and common step wording are sent to Anthropic. Nothing is sent while the setting is off.

The draft is shown first. You add it or discard it.

Built on Atlassian Forge. The app's code and data stay on Atlassian's infrastructure; it only contacts your Git provider or Anthropic when you turn those features on.

Examples:

The price, written down before you install.

One price per user, the same for every feature. Free for small teams, and a lower price per user above 100 users.

Examples: price per month

Jira users	you pay	how
up to 10	$0	free, all features
25	$30.75	25 × $1.23
50	$61.50	50 × $1.23
100	$123	100 × $1.23
250	$288	100 × $1.23 + 150 × $1.10

Pricing details and a quick calculator →

# Questions

Before you ask

Is it available now?

Not yet. The app is in final development and will be published on the Atlassian Marketplace. Ask for early access and we'll tell you when it's live.

Does my data leave Atlassian?

Only if you turn on Git sync (to your repository) or AI drafts (to Anthropic, with your key). Everything else stays in Atlassian's Forge storage on your site. See the privacy policy.

Which Git providers work?

GitHub, GitLab.com and Bitbucket Cloud. Self-managed GitLab and Bitbucket Data Center are not supported yet.

How is billing handled?

Through the Atlassian Marketplace, like any Jira app. Atlassian handles invoices and taxes.

Can I bring scenarios from another app?

Yes. Upload the .feature files or a zip exported from your current BDD app or taken from Git. See the import guide.

What if a feature I need is missing?

Tell us. We build the most requested features first and tell you personally when yours ships.

Move before 31 January 2027, not on it.

Tell us which app you use today and roughly how many Jira users you have. We'll write when Gherkin Studio is live.

Get early access