Requirement managers can import multiple requirements or 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). Any user can export a list of requirements and stories.
- Exporting items from the change grid
- Importing requirements
- Importing stories
Exporting requirements and stories
Any user can export either requirements or 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 requirements or stories that re 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 and stories 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 three dots menu on 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 a 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)
- Required by date (format should be MM/DD/YYYY or YYYY-MM-DD)
- Required by reason
- How might it 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.
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 story grid and select the three dots menu next to “Add new” button in the upper right corner of the grid. You will still be able to choose whether the stories should be uploaded to a specific requirement of should they stand alone.
CSV file import format for stories import
- Summary (mandatory field)
- As a" (mandatory field; need resource manager permission if creating new resources in the space; cannot be of "closed" category )
- I want to" (mandatory field)
- "So that I can" (mandatory field)
- Story ID (mandatory field)
- Status (must match one of the space status values)
- Tags: (space separated list - currently at least 1 tag is required )
- Acceptance criteria
If the system finds a matching story ID during upload, it will update the existing story with the new information. If no matching ID exists in the system, a new story will be created using the next number in the sequence, not necessarily the number supplied in column E.