Gherkin for Jira
Feature Files keeps Gherkin scenarios where they belong — in .feature files — while
letting analysts and QA work with them inside Jira. The link between a scenario and an issue is a
tag in the file itself, so it survives being renamed in somebody's editor.
Project navigation → More → BDD. There is also a panel on the issue itself, showing the scenarios tagged with that issue key.
@ACME-42 to its tags. One scenario can
carry several issue tags, and one issue can have many scenarios — the relationship is genuinely
many-to-many.Paste or upload a set of .feature files and the app creates them as they are,
including tags. The export is written to be read back by that same import, so a round trip through
Git loses nothing.
Every scenario in the project on one page, filterable by tag, feature or issue. This is the page to send to somebody who asks what the product actually does.
Receiving results from your pipeline is built and switched off. Any web trigger module — even an inbound one — costs the app its Runs on Atlassian badge, and for most buyers that badge is worth more than the feature. If you need it, write to us and we will talk about turning it on.
Scenarios can no longer be changed or imported. Reading, living documentation and both exports keep working, always. The whole point of this app is that the scenarios are yours and live in files; locking them inside the app would contradict its own listing.
Write to support@avakode.com. Questions that arrive twice get added to this page.