Additional Tasks
For an easy migration of backlog items from other systems a CSV import can be carried out by product owners.
To import backlog items, perform the following steps:
- On your personnel dashboard or on a scrum project execute the “Import Backlog Items” context menu command.
- Enter the path to the CSV file in the Content field.
Note: Click the “Download CSV Template” button to retrieve a template that describes the necessary data structure. - Click “Start Import”.
- After the import has finished, click “Next”.
Data structure of the CSV file
CSV Column | Description |
|---|---|
Type | the type of the backlog item (Story, Defect, Impediment) |
ImportID | an arbitrary unique key to identify the item in recurring imports (string) |
ScrumProjectID | the target scrum project (Fabasoft Cloud ID) |
Title | the Subject of the backlog item (string) |
Feature | the Feature of the backlog item (Fabasoft Cloud ID) |
State | the State of the backlog item (Received, Planning) |
Priority | the Priority of the backlog item (SPT_A_MUST_HAVE, SPT_B_SHOULD_HAVE, SPT_C_COULD_HAVE, SPT_D_WONT_HAVE) |
Order | the Order of the backlog item (integer) |
StoryPoints | the Size of the backlog item (F_0, F_1, F_2, F_3, F_5, F_8, F_13, F_21, F_34, F_UNDEFINED) |
Story | the description of the backlog item (quoted string) |
AcceptanceCriteria | the Acceptance Criteria of the backlog item (quoted string) |
CreatedAt | Created on/at of the backlog item (format: yyyy-mm-dd hh:mm:ss) |
Note:
- Backlog items can be updated during a new import, but only if the state has not changed in the meantime.
- When importing via the personnel dashboard the scrum project ID has to be specified, if multiple scrum projects exist.
- When importing via a scrum project only entries are imported whose scrum project IDs are either empty or correspond to the current project.