- 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
- Create New Entities with an Imported CSV File
- Update Existing Entities within Import from CSV Files
Import Effort for User Stories, Tasks, Bugs, Requests
It’s possible to import both the total effort for multiple roles and the effort for a single role, depending on how many responsible roles you’ve got for an entity.
Let’s say, you have User Story with two responsible roles: Developer and Tester. In this case, the effort is split. For example, you want to import a User Story that has 12 hrs of effort in total, but the Developer effort is 7 hrs and the Tester effort is 5 hrs.
You should enter the effort in the following format:
(Developer) 7, (Tester) 5
The general format is:
(role) effort value, (role) effort value, (role) effort value
For a single responsible role, just enter the effort value:
Here is an example of how you can import a User Story and several Tasks. Note that User Story has two roles: Developer and QA Engineer
If there are two responsible roles for a User Story, be sure to specify effort for both the roles in the Effort column, otherwise Effort will not be imported.
Import Estimates for Features, Epics, Portfolio Epics
You can import estimates to portfolio backlog items within numeric custom fields. Additionally you're welcome to configure an Automation rule to copy estimates from a custom field to the dedicated "Initial Estimate" field for each Feature, Epic, Portfolio Epic. Should you require an assistance with importing portfolio backlogs, please contact our Support Team.