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.
- Exporting user stories
- Importing user stories
- CSV file format
- Import rules
- 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 "three dots" 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
- Summary (mandatory field)
- Story Id
- Status (must match statuses in the Space)
- Tags (have to be single strings of characters and cannot include special symbols like = _ > < ! % $ etc. )
- Acceptance criteria
- System ID (leave this empty unless you know the unique string ID from the export file)
- External ID (provide if you are importing stories from a different system, like JIRA accelerator, ServiceNow etc.)
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.