# Export User Journeys & Acceptance Criteria

## User Journeys

You can export a Story's User Journeys to a Comma-Separated Value (CSV) file. This is useful to save time creating comprehensive test cases and test plans in work management tools like JIRA.

On the Story toolbar, click the **Download** button and select **User Journeys (.csv)** from the menu:

<figure><img src="https://619360366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvFE09GWUQiR5kjeutlr2%2Fuploads%2FY9cxH9qsiDW6CAa6wpKJ%2FScreenshot%202025-01-12%20at%2012.16.21.png?alt=media&#x26;token=6e1861dc-191f-4e56-bb4e-d36274eea62f" alt=""><figcaption></figcaption></figure>

### CSV file structure

* `Goal` number
* `Step` number, within the Goal
* `Action` text. If the connection into the Action has a label, it is incorporated into the Action text.
* Action `Notes`

<figure><img src="https://619360366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvFE09GWUQiR5kjeutlr2%2Fuploads%2FDw5Jg7uzmGFra8tFEEzj%2FScreenshot%202025-01-12%20at%2012.17.45.png?alt=media&#x26;token=8465233d-094a-42dc-86c5-4a0b3d6b27da" alt=""><figcaption></figcaption></figure>

##

## Acceptance Criteria

You can export a Story's Acceptance Criteria Gherkin -style Feature/Scenarios to Feature (.feature) files.&#x20;

{% hint style="warning" %}
This does not export the Role, Goal, and Benefit statement
{% endhint %}

This is useful if you use Behavior Driven Development **(**&#x42;DD) tools (or add-ins) in platforms like JIRA, or directly in the [Cucumber](https://cucumber.io/) test automation tool.

On the Story toolbar, click the **Download** button and select **Acceptance Criteria (.feature)** from the menu:

<figure><img src="https://619360366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvFE09GWUQiR5kjeutlr2%2Fuploads%2FrJx67T5K0pAxz11zR2A3%2FScreenshot%202025-01-12%20at%2012.23.15.png?alt=media&#x26;token=b6b0fbe1-430a-4054-bebf-8a7a3b98848c" alt=""><figcaption></figcaption></figure>

### Feature file structure

Flowriter will prepare a separate `.feature` file for each scenario. The files will be downloaded in a single ZIP file that when expanded will look similar to this:

<figure><img src="https://619360366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvFE09GWUQiR5kjeutlr2%2Fuploads%2FFrHDFyU1NCkut0ATTJN7%2FScreenshot%202025-01-12%20at%2012.24.58.png?alt=media&#x26;token=86d7ba02-88a9-4b3e-8778-bed1cdbf1529" alt="" width="563"><figcaption></figcaption></figure>

Each `.feature` file has this internal format:

<figure><img src="https://619360366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvFE09GWUQiR5kjeutlr2%2Fuploads%2FeHlwh0WWCPfE4kXNiN07%2FScreenshot%202025-01-12%20at%2012.26.28.png?alt=media&#x26;token=be6db8ff-0f1e-4d21-b4f0-136d4fc30473" alt="" width="563"><figcaption></figcaption></figure>
