FAQ

Does anything leave Atlassian?

No. Scenario Book has no servers of its own and sends nothing outside Atlassian. If you turn on pipeline sync, your own pipeline downloads your files into your repository, with credentials you give it.

Who can see published feature files?

While pipeline sync is on, the project's feature files are copied into Jira project properties, which anyone who can browse the project can read. That is the same audience as the project's Read tab. Turning sync off takes the copies back.

Will sync ever overwrite our work?

Not without a person choosing. If both sides changed the same scenario, it becomes a conflict on the story. Changes to different scenarios in the same file are both kept.

Which Gherkin languages work?

Any language the Gherkin parser supports, set with a # language: line at the top of a file. Keywords stay in your team's language.

Which test tools?

Anything that writes Cucumber JSON, Cucumber Messages or JUnit XML: Cucumber, Reqnroll and SpecFlow, Behave, Behat and others.

How big can a project be?

One feature file up to 1 MB. One import up to 16 MB of feature files, from a zip of up to 50 MB; split larger projects across imports. One pipeline call up to 4 MB and 100 files; the script splits bigger pushes.

What is kept, and for how long?

The last 50 versions of each file, deleted files for 30 days, and the last 50 test runs per project (a project admin can set 1 to 1,000). See Privacy.

What if our license lapses?

Editing, import, and your pipeline's pushes and results uploads stop. Reading, export and undoing an import keep working.

Why does it say "a teammate" instead of a name?

Scenario Book doesn't ask Jira for permission to read user profiles, so it stores account ids only and never names or email addresses.