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).
Prerequisites
Export: This can be done by any user.
Import: This can only be done by a user with a requirement manager permission.
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.
There are 2 export options:
Export to CSV: this format only includes the standard fields and IDs
Export to Excel file: (being improved, currently unavailable)
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
Only the following fields (columns) should be included in the CSV import file.
The CSV import file must have all the columns listed below, even if some are left blank for stories being imported.
The order of columns in the CSV import file must be the same one as outlined below. We match stories not by field name but by field order during the import process.
Summary:
mandatory field
name of the story (minimum 2 characters, maximum 255 )
Story ID:
mandatory field
sequential number of the story must be unique within space
Assigned to:
optional field
only accepts email address (john@example.com)
email address must match one of the existing users in the space
Description:
optional field
text field explaining the purpose of the story
Affected Roles:
optional field
lookup to resource collection
must match an existing resource in the Space
Acceptance criteria:
optional field
text field explaining the criteria to meet for story to be considered done
How might it be implemented:
optional field
text field explaining how the story might be implemented
Status:
mandatory field
must match existing statuses in the story workflow
Risk:
optional field picklist
value explaining the level of risk a story poses to the system
filled out, only accepts values: Low, Medium, or High
Release:
optional field
lookup to release
if filled out, must match the name of the existing release in the Space
Tags:
optional field
does not accept special symbols like = _ > < ! % $ etc.
new tag can be imported but it needs to be a single string of letters and numbers only
multiple tags can be imported but they must not be comma separated, instead they need to be separated by a space, like "Tag1 Tag2 Tag3"
Parent requirement:
optional field
if filled out, must match the Requirement ID (sequential number, unique in a space) of an existing requirement in the Space
Custom fields:
optional: if you have custom fields on your stories, you can include them in your CSV import file. If a custom field is 'required' on a story, you must include it in the import file.
if a required custom field is empty in your CSV file, we will import the file but show notification of partial import.
if custom field is filled out, it must support the same data format as the field in the Space. For instance, a 'date' field will only accept numbers, not letters or rich text.
custom fields must be included in the CSV import file in the same order they appear in the setting page.
Import rules
If we find a requirement/story with the matching ID on the grid
we update that story/requirement with imported data, irrespective of the status of the existing records in Elements
we will not create a new story
If we do not find a requirement/story with the matching ID
we create a new record (requirement/story) in Elements
If custom fields are required and they are empty in the CSV file to be imported:
if they are empty in the CSV
If we import requirements/stories with IDs: 1, 2 and 4, upon import these requirements/stories have IDs: 1,2 and 4, and not 1,2 and 3 (we do not force renumbering to be sequential)
If requirement/story records are to be updated in Elements using a CSV file, the full template should be imported irrespective of what field is to be updated.
Troubleshooting / FAQ
Here are some common issues that happen with manual CSV imports of stories:
Unnecessary standard fields included:
If you exported list of stories from Elements, then the export file likely contains fields like 'Conflict", "JIRA ID,"JIRA dev project", and maybe others. These fields are not supported in the import and should be discarded.
Wrong data format:
you need to ensure that the data format in the import file matches the expected data in Elements. For instance, users often fill out the 'Assigned to' field with name and surname instead of an email.
Import creates new stories instead of updating existing ones:
check that the story ID (CSV and Elements) matches
Wrong order of custom fields:
custom fields can be imported with the stories but they must be added as columns 14 and onwards in the CSV file
the order of columns representing custom fields must be the same as they are listed in the settings page.
Import was successful but I cannot see the updated fields in Elements:
check that you are not on a custom view of requirement/story. Fields that were not added to a custom view will not be visible after a successful import.