Import / export user stories

Export; Import; User Story

Ksawery Lisinski avatar
Written by Ksawery Lisinski
Updated over a week ago

You can export and import multiple user stories (or bulk-update existing ones) from a CSV file (you can export a CSV file from any spreadsheet software like Excel or Google Sheets).

For JIRA import, check this article.

Article outline

  • Prerequisites

  • Exporting user stories

  • Importing user stories

  • CSV file format

  • Import rules

  • Exceptions


Exporting user stories

Any user can export user stories from the grid. You need to click on the "Import/Export" menu item in the toolbar and then select one of the export options. The export file will only contain the user stories that are currently present in the grid, i.e. if you apply any filter only the filtered list will be exported.

  • Export via Excel file: this format includes all fields (all columns)

  • Export via CSV: this format only includes the standard fields and IDs

When exporting a list of user stories, the linked processes, Salesforce org model items, and additional attachments are not included.

Importing user stories

There are 2 ways to import stories. You can either import stories to a specific requirement or as stand-alone stories.

To import a CSV file with stories for a particular requirement, you must click on "Import from CSV" text button in the stories tab for the selected requirement in the right sidebar.

You can also import stories as stand-alone. Switch to the Stories grid and select the "Import/Export" icon in the upper right corner of the toolbar. You will still be able to choose whether the stories should be uploaded to a specific requirement or if they should stand alone.

CSV file import format for stories import

  1. Summary (mandatory field)

  2. Story Id

  3. Assigned to (must match the email address of an existing user in the Space)

  4. Description

  5. Affected Roles (must match an existing resource in the Space)

  6. Acceptance criteria

  7. Status (must match statuses in the Space)

  8. Risk

  9. Release (must match the name of an existing release in the Space)

  10. Tags (have to be single strings of characters and cannot include special symbols like = _ > < ! % $ etc. )

  11. Parent requirement (must match the requirement ID of an existing requirement in the Space)

  12. System ID (leave this empty unless you know the unique string ID from the export file)

  13. External ID (provide if you are importing stories from a different system, like JIRA accelerator, ServiceNow etc.)

  14. Any custom fields you may have added. These should be formatted in the order they appear in the grid.

For example:

TIP If you already have stories in Elements you can get the correct import format by exporting your stories first, and using the format given.

Import rules

If a story record in a CSV file has the external ID provided, then:

  • if we can match it to an existing story's external ID (one that was imported before), we will update the existing story;

  • if we cannot find an existing story with the same external ID, we will create a new story with that external ID.

If a story record in a CSV does not have the external ID provided, then:

  • if we can match it to an existing story's system ID AND the existing story does not have an external ID, we will update the existing story;

  • if we can match it to an existing story's system ID BUT the existing story does have an external ID, we will create a new story;

  • if we cannot match it to an existing story's system ID we will create a new story.

If you have any issues, feedback or requests, please reach out to us at and we can help you.

You might be also interested in

  • User stories - to be able to get the right solution, you really have to start from defining the problem by getting into the shoes of who is going to face the issue

  • Sharing requirements and stories - in order to share a requirement or a user story with other users and collaborate on it, you need to copy a unique URL from the Share tab

  • Reporting on requirements - reporting is a very useful feature which can be used creatively to access knowledge quickly and/or manage the progress of work within Processes

  • JIRA integration - you can connect your Elements Space with multiple JIRA projects in multiple domains and send stories for development

  • Business requirements - business requirements are a tool for documenting your business needs for driving higher value in your company

Did this answer your question?