Gherkit: BDD Scenarios and Gherkin for Jira

Highlights

1. A Gherkin editor that catches mistakes

   Syntax highlighting, instant checks for broken tables, missing Examples columns and stray steps, one-click formatting, and step suggestions from the rest of your project.

2. Living documentation for every project

   Every scenario in one place: filter by tag or by result, open any feature, and export the whole project as .feature files in one of three folder layouts.

3. Results from CI on the issue

   A one-file helper pulls scenarios into your pipeline and sends Cucumber results back. Failing scenarios get a red marker and the error message, right on the story. You can also filter with JQL: gherkitStatus = failed.

Screenshots

More details

• Your data stays in Jira. Scenarios are stored on the issues themselves, readable with Jira's own REST API. Gherkit has no servers and makes no outside calls: it runs entirely on Atlassian.
• No lock-in. Export everything as plain .feature files at any time.
• Cucumber-compatible results: tested with cucumber-js. Cucumber-JVM writes the same JSON report. Other runners (Behave, SpecFlow/Reqnroll, Behat) need a Cucumber JSON formatter or converter. (Cucumber is a trademark of Cucumber Ltd / SmartBear; Gherkit is not affiliated with them.)
• Moving from another BDD app? Upload your existing .feature files, or a zip of your features folder. Each file lands on the issue named in its @KEY tag (above "Feature:" or on its scenarios) or at the start of its file name. You see a preview before anything is written. See the migration guide.
• Built for teams: conflict detection when two people edit at once, version history with restore, JQL fields for dashboards (gherkitScenarios, gherkitTag, gherkitStatus, gherkitLastRun).