Import and Export Data

You can import data into CA Agile Central or export data from CA Agile Central into another application.

NEW: If you are importing test cases, read more here.

Import Data

Import data from other products into CA Agile Central using a comma separated value (CSV) formatted file. From each summary page in CA Agile Central, you can choose an Import option from the Actions drop-down to launch an import wizard.

Page Menu option
Backlog Import User Stories
User Stories Import User Stories
Iteration Status Import User Stories
Import Tasks
Portfolio Items (Requires CA Agile Central Portfolio Manager) Import Portfolio Items
Tasks Import Tasks
Defects Import
Test Cases (Requires CA Agile Central Quality Manager) Import Test Cases

When importing data, be sure to consider the following:

Note:

  • Eliminate duplicate work items prior to importing; if you have duplicate work items in your CSV file, you will have to manually fix them.
  • You cannot update existing work items with the import function; new work items are created, causing duplicates.
  • You cannot import associations between work items, such as parent- child story relationships.
  • You cannot import test case steps.
  • The schedule state of a task you import can update the state of the user story or defect it is associated to.
  • For advanced imports including relationships, see CA Agile Central Add-in for Excel.

To import a CSV file:

  1. From the summary page you need to import work items from, select Actions, Import.
  2. On the Import pop-up, verify your CSV file is correctly formatted by selecting the hyperlinked import template.
    The header columns in these templates must be exactly reproduced in your CSV file for successful import. Each template can be modified for your import.
  3. Select Browse to locate your CSV file.
  4. Select your file and select Open.
  5. Optionally, select the advanced hyperlink to specify your character encoding.
  6. Select Import and your data is imported and displayed at the end of the summary view.

Caution: If drag-and-drop ranking is enabled and you attempt to export a view and re- rank your data outside of CA Agile Central, your export will reflect a page order rather than a rank number. Upon importing the data, your new page order will be preserved; however, the imported work items will be appended to the end of the view. Existing work items are not overwritten, but instead are treated as new work items.

Data is added to the top of the summary view.

If the path to your import file location is 256 characters or greater and your operating system is Microsoft Windows, your file cannot be imported. This is a limitation of Windows.

If your administrator has marked some fields as required, you must provide values for those columns in the CSV file.

Any custom values or custom fields you have added to a work item are included in the related data import template. Standard fields are listed first, followed by custom fields.

Importing a file that has been exported from the parent project will only import into the current project. It will not import into multiple projects.

Data Import Specifications

Different work items offer different levels of data import. Use the following table to guide you when importing work items.

Note: If you are attempting to import test cases that contain multiple test steps, we recommend that you use the CA Agile Central Add-in for Excel.
Import Imported Fields Field-Level Specifications
User stories
Name Limited to 256 characters
Description Limited to 32K (imported through a CSV file)
Package  
Risk  
Backlog State  
Backlog Rank  
Owner Desired owner's username
Notes  
Defect
Name Limited to 256 characters
Description Limited to 32K (imported through a CSV file)
State Valid values are: Open, Closed, Submitted, Fixed
Package  
Severity Valid values are: Crash/Data Loss, Major Problem, Minor Problem, Cosmetic, None
Submitted By  
Environment Valid values are: Production, Test, Development
Found in Build Maximum length of 128 characters
Priority Valid values are: Resolve Immediately, High Attention, Normal, Low, None
Owner Desired owner's username
Affects Doc T/F  
Release Notes T/F  
Target Date  
Target Build  
Fixed in Build Maximum length of 128 characters
Resolution Valid values are: Architecture, Code Change, Configuration Change, Database Change, Duplicate, Need More Information, Not a Defect, Software Limitation, User Interface
Verified in Build Maximum length of 128 characters
Notes  
Task
Name Limited to 256 characters
Description Limited to 32K (imported through a CSV file)
Work Product Required field; enter the FormattedID of the associated work item (ex, US123 or DE456)
State  
Owner Desired owner's username
Estimate  
To Do  
Blocked
T/F
 
Ready
T/F
 
Blocked Reason Limited to 256 characters
Package Valid values are determined by their values in configuration for the current workspace
Notes  
Actuals  
Test case
Name Limited to 256 characters
Description Limited to 32K (imported through a CSV file)
Notes  
Owner Desired owner's username
Test Folder Parent folder of the test case (ex, TF123)
Work Product Enter the FormattedID of the associated work item (ex, US123 or DE456)
Objective Maximum of 2k (text only)
Type Valid values are determined by the test case type values in configuration for the current workspace
Method - Manual/Automated Valid values are Manual and Automated (case-sensitive)
Priority Valid values are determined by their values in configuration for the current workspace
Risk Valid values are determined by their values in configuration for the current workspace
Package Valid values are determined by their values in configuration for the current workspace
Last Verdict Valid values are determined by their values in configuration for the current workspace; if Last Verdict, Last Build, and Last Run are contained in the CSV import file, a test case result is created for the test case
Last Build For the test case result, limited to 128 characters; if Last Verdict, Last Build, and Last Run are contained in the CSV import file, a test case Result is created for the test case
Last Run Must be a valid date formatted the same as your user Date/Time format set in user profile settings; if Last Verdict, Last Build, and Last Run are contained in the CSV import file, a test case Result is created for the test case
Portfolio Item
Investment Category  
Planned End Date Use date format mm/dd/yyyy
Planned Start Date Use date format mm/dd/yyyy
Portfolio Item Type Required field
Preliminary Estimate  
Risk Score  
Value Score  
Name  
Description  
Notes  
Owner Desired owner's username
Ready  

Format Files for CSV Import

The import dialog contains a link to download data import templates which helps you format your CSV file correctly to ensure all your data is imported. Each work item has a specific data import template which provides a format for all fields contained within the work item. To successfully import a file, the column headers must match those present in the data import templates. CA Agile Central suggests you download the provided template to verify correct formatting each time before you import your file. Each template can be modified for your import.

The first line of the data import template consists of column headers. The second line of the template contains sample data.

CSV file formatting considerations:

  • Fields are separated by commas and enclosed in quotes if they contain commas or quotes.
  • Embedded quotes in your input data are doubled.
  • Embedded spaces do not require surrounding quotes.
  • There is no comma following the last field on the line.
  • Null fields are represented by two consecutive commas.
  • Leading and trailing spaces on fields, even inside quotes, are ignored.
  • File must normally end with a single CrLf (Carriage return, Line Feed or both).
  • The length of the path to your CSV file may not exceed 255 characters.
  • Both Windows and non-Windows file browsing are supported.

You will be prompted with message dialogs from CA Agile Central should the following situations occur:

  • Importing a file greater than 2 MB
  • Missing or incorrect header
  • Invalid value for boolean fields: valid values are t, T, F, f, True, False, true, false
  • Invalid, non-numeric values in numeric fields
  • Invalid date formats: all dates must be formatted as mm/dd/yyyy
  • Invalid user name fields ( Owner , Submitted By) if the user name does not exist
  • Importing a non-CSV file format
  • Importing fields with case-sensitive list values that do not match
  • Importing an empty file

Export Data

You can export user stories, test cases, defects, releases, iterations, portfolio items, and tasks. You can export your data to a CSV or XML file. Open this file with any application that can access CSV or XML file format and manipulate your data to display in charts, reports, and other presentations. The date and time format in your exported data will have the following format: 2016-05-10T21:26.13.984Z.

  1. From the summary page you want to export work items from, select Actions and select a format:
    • CSV
    • XML (not available on all summary pages)
  2. On the Export pop-up, specify whether you want to open or save the file.
  3. Select OK.

The CSV option exports the fields that are currently displayed on the summary page. Create a custom view to include additional fields to get your desired export data.

Note: If you are trying to export to CSV and have special characters like Unicode UTF-8 characters, you will need to open the export with an application that is configured to read UTF-8 characters. Otherwise, the characters will not appear in your export.

Child user stories are exported and ordered by parent user story rank, then hierarchy and child user story rank. The Parent ID field contains the ID of the parent user story.

You must have at least edit-level security to export a work product.

If drag-and-drop ranking is active and you attempt to export a view and re-rank your data outside of CA Agile Central, your export will reflect a page order rather than a rank number. Upon importing the data, your new page order will be preserved; however, the imported work items will be appended to the end of the view. Existing work items are not overwritten, but instead are treated as new work items.

XML Export

Note: If you are using the XML export option and have a large data set containing thousands of work items, the export may time out causing the export to fail. To avoid this, reduce your data set or use the CSV export option or CA Agile Central Add-in for Excel.

XML exports references to the objects, not the actual child collections. Collections include:

  • Artifact → Changesets
  • Artifact → Tags
  • Build → Changesets
  • BuildDefinition → Builds
  • BuildDefinition → Projects
  • Change → Artifacts
  • Change → Builds
  • Change → Changes
  • Defect → Changesets
  • Defect → Duplicates
  • Defect → Tasks
  • Defect → Test Case Result
  • Defect → Test Cases
  • Defect Suite → Defects
  • Defect Suite → Tasks
  • Userstory → Changesets
  • Userstory → Children
  • Userstory → Defects
  • Userstory → Predecessors
  • Userstory → Successors
  • Userstory → Tasks
  • Userstory → Test Cases
  • PortfolioItem/ Feature → UserStories
  • PortfolioItem/Initiative → Children (PortfolioItem/Feature)
  • PortfolioItem/Strategy → Children (PortfolioItem/Initiative)
  • Project → BuildDefinition
  • Project → Children
  • Project → Editors (Users)
  • Project → Iterations
  • Project → Releases
  • Project → TeamMembers (Users)
  • SCMRepository → Projects
  • Subscription → Workspaces
  • Test Case → Results (Test Case Results)
  • Test Case → Steps (Test Case Steps)
  • TestFolder → Children ( Test Folder )
  • TestFolder → TestCases
  • TestSet → Tasks
  • TestSet → TestCases

Import Test Cases

This feature allows you to import multiple types in one file as well as test case steps.

Caution: When editing the template in Excel, be sure to specifically save it as a CSV file. Excel can change the format of your file and rearrange columns. The error message you will receive is "Line 0: You must include an Object Type column."

Notes:
  • Any time you do an import with the importer, you will have to specify the ObjectType. If you don't enter a value in this field, you will get an error, regardless of whether you're importing one or multiple work item types.
  • When you download the import template, the sample values in line two will display “(required)” next to sample values for required fields.
  • Each line is individually processed and saved, and only the lines that fail are not imported. If you have failures and re-run the same file, you will have duplicate objects.
  • The Project field cannot be imported; all artifacts that are imported will be added to the current project.
  • If you import test case steps to a test case that already has steps, the test case steps in the import file will always be appended to the list of existing test case steps.
  • Enter the user ID to set an owner on import.
  • The fields and sample values in the import template are specific to test cases. If you want to import test case steps (or any other type of data), include the required fields as columns in the import file. You can edit an existing test case to view the required fields for a test case step.

 

Certain fields cannot be imported. For example, when you import a test case, using the test sets field will not associate it to a test set . You won't see an error message for these fields since you can import item types in a single file. Some other examples of fields that cannot be imported includes:

When importing these (in the Object Type field)... You cannot associate these on the same line:
Test cases Test sets, Rank
Test set Test cases
Test folders Test cases

Once enabled, users can use this new import option from the Test Cases page.

Import Multiple Types in One File

This requires an Object Type column. The value should be the type name of what you’re importing, such as Test Case, Test Case Step, etc.

For any properties that are not applicable to a particular object type, add a blank value.

Associate a Test Case Step to a Test Case on a Previous Line

In the Test Case column, use the line[2] syntax to indicate that you want to refer to the object created at line 2.

There are two options for importing test case steps into an existing test case.

Option 1 - Copy the Formatted ID of the New Test Case

After you create and save a new test case, copy its Formatted ID. Create a CSV using that formatted ID for your Test Case Steps. Choose that file for import, and when it's completed, you will notice that your newly created test case now has test case steps.

Use the Formatted ID of the Test Case in the Test Case column.

Note: If you refer to a recycled or deleted item, that line with fail on import.

Option 2 - Use the WSAPI Reference

Alternatively, you can use the WSAPI reference of the test case in the Test Case column.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.