Importing data into DevOps Plan using Import feature
The DevOps Plan application. There are two primary methods for bulk data import: using sample data and uploading a zip file.
feature allows teamspace admins or userdb super-users to add data to theUsing sample data
Certain schemas, such as Agile, FullSAFe, and DefectTracking, come with sample data for demonstration purposes. This sample data can be imported during application creation by selecting the Import sample data check box. Alternatively, it can be imported after creation via the option. When importing sample data during application creation, an extra box will indicate the import status. After creation, the option can be used to upload your own zip file or utilize the provided sample data. Select the Use sample data toggling option and click Import to import the sample data. A progress screen will display the import status, highlighting any warnings or errors. For instance, a warning might indicate a duplicate "Release" record named "Pizza 1.0".
Uploading a zip file
To upload your own data, you can clear the Use sample data toggling option and click Choose file to upload a zip file (up to 1MB). For larger data sets, multiple import operations may be necessary. The zip file should contain a bill of materials (bom.txt), one or more CSV (comma-separated values) files with record data, and a substitution.json file for data transformations. The import process and required file formats are detailed in the documentation.
- For Agile schema, click here.
- For FullSAFe schema, click here.
- For DefectTracking schema, click here.
Import data format
To build your own zip files for import, include three types of files:
- bill of materials (bom.txt)
- substitution file (substitution.json)
- CSV files
The bill of materials lists the CSV files and their corresponding record types. For example, it might include records for Sprint, Release, Component, Project, and WorkItem.
The substitution file modifies data during import, using strategies such as replaceExact, relativeDate, replaceAll, and override.
CSV files should follow the RFC4180 standard, with key points including field delimiter (comma), quote delimiter (double quote), record separator (carriage return and linefeed), and handling of empty lines and multiline values.
For stateful records, specify a unique identifier as the id value to ensure references are correctly re-established. DevOps Plan generates its own id values during import and stores the original id in the old_id field. This field should exist in all out-of-the-box schemas. If your workflow lacks the old_id field, reference imports may fail.
For stateless records, the id is automatically created from the record's field values, so the id column is not needed in CSV files for stateless record data.
For more details on the format of the files, click here.