Exporting work items
You can export data from work items to an HTML or comma-separated
values (CSV) file. You define the scope of the export operation by
specifying a query. After you export work items to a CSV file, you
can import them into another project area.
Before you begin
Important: The following data is not preserved
when you use the Export Work Items wizard to export item data to a
CSV file:
- Work item history
- Approval history
- Attachments
- All Open Services for Lifecycle Collaboration (OSLC) Uniform Resource
Identifier (URI) reference links. For example, Contributes To, Tracks,
Affects Plan Item, Affected By Defect, Related Change Request, Tracks
Requirement. As a result, while you can use the Import Work Items
wizard to import work items in CSV files that include URI reference
links, the import operation does not automatically create the backlinks
in the referenced items.
In contrast, standard reference links, such as Parent, Children, Duplicated By, and Depends On, are preserved when you export data to a CSV file.
Tip: The list of OSLC link types varies depending on project association definitions and the OSLC integrations that are configured. For a list of OSLC link types for the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications, see the following topics:- For the CCM application:
- For the QM application:
- For the RM application:
About this task
Procedure
Results
When you export work items by using the Export Work Items wizard, the first row of the CSV file contains attribute names. The Import wizard uses this first row to map the column values to attributes.
What to do next
Watch videos CLM playlistJazz.net channel User Education channel |
Learn more CLM learning circleAgile learning circle Learning circles |
Ask questions Jazz.net forumdeveloperWorks forums |
Get support Support PortalDeployment wiki Support blog |