SEE ALSO:
Brief summary of this article:
You can import CSV (comma-separated values) files for Portfolio Epics, Epics, Features, User Stories, Tasks, Bugs, Requests, Requesters, Users, Test Cases, Impediments in Targetprocess.
Entity-Specific Guides
These guides describe importing of entities of specific types in a detailed way:
Common fields
Here’s the list of the common fields that can be updated with import:
| Field / Entity Type | Usage Notes | Portfolio Epic | Epic | Feature | User Story | Task | Bug | Request | Test Case | Impediment |
| Name | + | + | + | + | + | + | + | + | + | |
| Project | Mandatory when 2 or more projects are currently selected | + | + | + | + | + | + | + | + | + |
| Description | Import as HTML code. Use <br> tags for line breaks. | + | + | + | + | + | + | + | + | + |
| Teams | + | + | + | + | + | + | + | |||
| Assignment
Developer |
+
since v3.13.10 |
+
since v3.13.10 |
+
since v3.13.10 |
+ | + | + | ||||
| Responsible | + | + | ||||||||
| Effort | + | + | + | + | ||||||
| State | + | + | + | + | + | + | + | + | + | |
| Team State | + | + | + | + | + | + | + | |||
| Release | + | + | + | |||||||
| Iteration
Sprint |
+ | + | + | |||||||
| Team Iteration | + | + | ||||||||
| Business Value | + | + | + | + | + | + | + | + | + | |
| Tags | + | + | + | + | + | + | + | + | + | |
| Custom Fields | + | + | + | + | + | + | + | + | + | |
| Creation Date
|
Can be set for new entities
Cannot be updated for existing entities |
+ | + | + | + | + | + | + | + | + |
| Owner | + | + | + | + | + | + | ||||
| Planned Start Date | Since v3.13.5 | + | + | + | + | + | + | + | + | |
| Planned End Date | Since v3.13.5 | + | + | + | + | + | + | + | + | |
| Start Date | Since v3.13.5 | + | + | + | + | + | + | + | + | |
| End Date | Since v3.13.5 | + | + | + | + | + | + | + | + |
Type-specific fields
These fields are specific to selected entity types.
| Entity Type | Fields |
| Portfolio Epic | None |
| Epic | Portfolio Epic (support in v.3.13.5+) |
| Feature | Epic Portfolio Epic (support in v.3.13.5+) |
| User Story | Feature
Valid entity type name spelling is UserStory. Make sure no spaces are in between.
|
| Task | User Story
User Story field is mandatory, even when you update an existing Task.
|
| Bug | Severity |
| Request | Requesters - it is possible to add Requesters within comma-separated list of emails. Requesters cannot be unassigned via Import. Targetprocess users cannot be added as Requesters via Import. Source Type |
| Requester | Company First Name Last Name Note Phone Creation Date Custom Fields |
| User | Email First Name Last Name Is Observer Login Password Role Custom Fields |
| Test Case | Use detailed guide for importing Test Cases and Test Steps.
Valid entity type name spelling are TestCase, TestStep. Make sure no spaces are in between. |
| Impediment | Parent (for Assignable) |
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.