You can export and import multiple requirements (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 user story import check this article.
- Exporting items from the change grid
- Importing requirements
- Export: This can be done by any user.
- Import: This can only be done by a user with a requirement manager permission.
Any user can export requirements 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 requirements 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
When exporting a list of requirements the linked processes, Salesforce org model items, and additional attachments are not included.
To import a CSV file for requirements, you must click on the icon shown below in the toolbar and select "Import from CSV".
Then drag and drop the CSV file from your desktop or select from the computer, clicking "Upload file".
CSV file format for requirements import
You can easily import requirements from another space (through the CSV file). If you want to import your requirements from a different system your CSV file needs to be in the following format (no header is required and you can leave non-mandatory fields as empty columns in your file):
- Summary (mandatory field)
- What is required?
- Status (must match one of the space status values and it cannot be of closed category)
- Requirement unique ID (mandatory field)
- Tags (have to be single strings of characters and cannot include special symbols like = _ > < ! % $ etc. )
- Required by date (format should be MM/DD/YYYY or YYYY-MM-DD)
- Required by reason
- How it might be implemented
The ID is an integer number. If the system finds a matching requirement ID during upload, it will update the existing requirement with the new information. The exception is if the ID belongs to a closed requirement - in which case the upload will fail as closed items cannot be changed.
If no matching ID exists, a new requirement will be created using the next number in the sequence, not necessarily the number supplied.
For example, if you have 2 existing requirements, they will be number 1 and 2. If you have three rows in the CSV file and all three have the ID 4 it will create the first row with ID 3, it will create the second with ID 4 and will then update the new requirement with ID 4 with the details from the 3 row of the CSV file.