How to import entities with Estimates and Role Effort

It is possible to create and update work items in Targetprocess using CSV files as data source. This article describes how to import or update Effort and Role Effort values.

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:

7

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.

See Also

• How to import entities with Assignments