- Import from CSV files
- Import Extendable entities
- How to import entities from a CSV file
- Entities and fields supported for import from CSV files
- Import User Accounts from CSV file
- Import Requesters from CSV file
- Update Existing Entities within Import from CSV Files
- Import Hierarchical Backlogs from CSV Files
Brief summary of this article:
It is possible to batch create new Targetprocess entities (User Stories, Tasks, Bugs, Features, Epics, Portfolio Epics, Requests) with CSV files. Within import you can set fields and properties of entities such as entity state, business value, custom field values, assigned tags, estimated effort, planned dates, assigned users and teams. This article describes how to perform the import.
Here's how a basic CSV file with list a of entities to be created looks when opened in a spreadsheet editor:
Files in CSV (Comma-separated values) format are commonly used to transfer data between spreadsheet editors (such as Microsoft Excel, OpenOffice, LibreOffice, Google Sheets) and other software systems and tools.
Importing from CSV files is one of the possible ways to create new entities in Targetprocess. It is also possible to create them using the Quick Add Several Work Items mashup and REST API calls.
This guide describes a basic use case where all the entities you import have the same entity type. For example, you import a list of User Stories or a list of Bugs. The Targetprocess Import wizard has advanced capability to import entities of multiple types in a single CSV file. This capability is described in the dedicated article: How to import a hierarchical backlog from single CSV file.
Supported Entity Types and Fields
A list of entities and fields that can be imported using CSV files is available in the dedicated article: Entities and fields supported for import from CSV files.
Entity-Specific Guides
These guides describe the importing of entities of specific types in a detailed way:
Required Permissions
A user who performs the import must have Add permissions for the selected entity type within the relevant Project(s). Administrators can import entities to any Project and assign them to any Team, even those they are not members of. For more information: Permissions for Access to Work Items.
How to Perform the Import
Upload your CSV file with data on the Settings > Import page. Then customize settings and map columns.
See the basic principles of importing CSV files in the dedicated article: How to import entities from a CSV file.
How to Prepare the CSV Data File
You can create a source CSV file manually. Use any available spreadsheet editor such as Microsoft Excel, OpenOffice, LibreOffice, Google Sheets. All of them support saving data in CSV file format.
Required Columns
To create a new Targetprocess entity you have to fill in and accurately map all the mandatory columns in the CSV file. For most of the assignable entities(User Stories, Tasks, Bugs, Features, Epics, Requests), the mandatory columns are Name and Project.
Name | Format | Notes |
Name | My Story | Name of the item you create. Maximal length is 255 symbols. Line breaks are not allowed. |
Project | 123
Alpha |
Numeric ID or Name of the Project the entity is added to. |
Add Entities to a Single Project
The Project column is not required when all the entities you create should be added to the same Project. You can exclude the Project column from your CSV file. Instead, select this single Project in the list of Projects displayed in Step 1 of the Import wizard.
Otherwise, you have to specify the Project for your entities. The Project column is required in your CSV file and should be mapped properly. In this case you may select none, or two and more Projects in Step 1 of the Import wizard.
Columns Mapping
Your source CSV file may also contain other columns with data for import to Targetprocess.
If some column in the file is not supported for Import, use the Skip option for the column during the mapping step. Also, you can Skip a supported column in order to not import values from it due to missing prerequisites, errors, or because it is not needed in the import.
Automate Creation of Recurrent Work Items
It may happen that some Tasks occur in your Project on a regular basis, such as weekly or monthly. Recurrent Tasks are not supported in Targetprocess so far. In the meantime, Import from CSV files is one of the workarounds that could save you time and speed up Task creation.
See Also
Still have a question?
We're here to help! Just contact our friendly support team.