Import backlog items
You can import backlog items from a file into the product or release backlog. User stories and defects are imported from separate files.
Tip:
- If you have access to multiple workspaces, be sure you are importing content into the correct workspace.
- Excel files exported from Agile Manager are not formatted in the same way as the import template files. If you export backlog items and import them elsewhere, first copy the content to an import file.
Prepare a backlog import file
In an Excel or CSV file, list the user stories or defects you want to import.
When importing from Excel, your import can also include tasks and acceptance tests. Add a Tasks sheet in a defect or user story import file, and/or an Acceptance Tests sheet in a user story import file.
The file must be formatted according to specific guidelines, and some fields are restricted to certain values. For more details, see Import guidelines and Fields and validations below.
Use template files to assist you in creating compatible backlog files.
Template Files
Agile Manager supports Microsoft Office Excel versions 2010 and 2013.
Import the backlog items into Agile Manager
-
Select the area in Agile Manager into which you want to import backlog items:
-
Product backlog: Under Product Backlog > Backlog, select the Backlog Items View.
-
Release backlog: Select Release Management > Release Backlog. Make sure the correct release is selected.
-
-
Click More Actions > Import Backlog.
-
In the Import Backlog dialog box, specify whether you are importing user stories or defects.
After Agile Manager validates the content of the file, you can import the backlog items.
Import guidelines
Review these guidelines to ensure that the import completes successfully. Many of the guidelines are implemented in the template files.
Import guidelines | |
---|---|
Supported file formats |
.xls .xlsx .csv |
Multiple Excel worksheets |
In Excel files, the main backlog item data must be in the first worksheet, or a worksheet named Backlog Items. Add separate sheets for Tasks or Acceptance Tests to include them in the import. |
Import file size | The import file can contain up to 2000 items to import, including backlog items, tasks, and acceptance tests. |
Field names and column headers |
The field names must be listed on the first row of the file or worksheet. The order of the fields is not important. The column headers in the file must match the field names in Agile Manager. |
Merging imported data |
You cannot merge an imported backlog item with an existing backlog item: if you import an item with the same name as an existing backlog item, another backlog item will be created with the same name. |
Supported fields |
You can include any of the standard user story or defect fields, in addition to any custom fields defined in your site. If you want to import data to custom fields, simply add additional columns for the additional fields. |
Required fields |
Some fields are required, and must be filled in for each user story or defect. For details, see Fields and validations below. Note: If your administrator has set additional fields as required for user stories or defects, they are not included in the templates by default. You must add them to the import file as additional columns, using the exact names of the required fields. You may want to mark these extra columns as required by adding a comment to the column header, and save the file as a template for later use. |
Supported field values |
Some fields may contain specific values only. For details, see Fields and validations below. |
Multi-list fields |
To specify several values in multiple selection fields, separate the values with a semicolon. |
Ranking | Backlog items are ranked in Agile Manager according to their order in the file. If backlog items are already defined in Agile Manager, the imported items are ranked below the existing ones. |
Themes, features, and applications | Themes and features can belong to multiple applications. If you add separate items with the same theme and feature name, but different applications, any new application values are added to the theme and feature when you import. |
Fields and validations
The following tables list the required user story and defect fields that must be filled in the Excel sheet for each backlog item, and the allowed values for certain fields.
First Sheet (User Stories)
Field * required |
Allowed Values |
---|---|
Name * | Free text, maximum 255 characters |
Description | Free text |
Story Points | Positive integer |
Priority |
Can include one of the following values: 1-High / 2-Medium / 3-Low |
Author* | An existing user's login name. |
Theme |
An existing or a new theme name. New themes will be added to the backlog. Theme names are case-sensitive. Note: You can specify a new theme even if the system administrator defined feature fields as required. Field requirements for themes and features are not enforced when you import backlog items. |
Feature |
An existing or a new feature name. New features will be added to the backlog. Feature names are case-sensitive. Note:
|
Application |
An application that is already defined in Agile Manager. Note: Depending on your workspace or user settings, this field may be required. |
Release |
To assign a user story to a release, type the name of a release that is already defined in Agile Manager. Tip: To import an entire file to a specific release, import it from the Release Backlog page. In this case, you do not need to fill in the Release field. |
Sprint | To assign a user story to a specific sprint, type the name of the sprint. The sprint must be included in the specified release. |
Team | To assign a user story to a specific team, type the name of the team. The team must be defined in the specified release and active in the specified sprint. |
ID |
A user story ID, unique within the import file. Required if importing tasks or acceptance tests. Used only to associate a user story with its tasks and acceptance tests, listed in the Tasks and Acceptance Tests sheets. |
First Sheet (Defects)
Field * required |
Allowed Values |
---|---|
Summary * | Free text, maximum 255 characters |
Description | Free text |
Story Points | Positive integer |
Severity * |
Can include one of the following values: 1-Critical / 2-High / 3-Medium / 4-Low |
Priority |
Can include one of the following values:
|
Defect Status * |
Can include one of the following values: New / Open / Fixed / Closed / Propose Close / Deferred / Duplicate / Rejected |
Detected By * | An existing user's login name. |
Detected on Date * | Must include a valid date. In an Excel file, make sure the Detected on Date cells are formatted as dates. |
Theme |
An existing or a new theme name. New themes will be added to the backlog. Theme names are case-sensitive. |
Feature |
An existing or a new feature name. New features will be added to the backlog. Feature names are case-sensitive. Note: If you specified a theme, you must specify a feature. |
Application |
An application that is already defined in Agile Manager. Note: Depending on your workspace and user settings, this field may be required. |
Release |
To assign a defect to a release, type the name of a release that is already defined in Agile Manager. Tip: To import an entire file to a specific release, import it from the Release Backlog page. In this case, you do not need to fill in the Release field. |
Sprint | To assign a defect to a specific sprint, type the name of the sprint. The sprint must be included in the specified release. |
Team | To assign a defect to a specific team, type the name of the team. The team must be defined in the specified release and active in the specified sprint. |
ID |
A defect ID, unique within the import file. Required if importing tasks. Used only to associate a defect with its tasks, listed in the Tasks sheet. |
Tasks Sheet
Field * required |
Allowed Values |
---|---|
Backlog Item ID * | The ID of the backlog item relevant to this task (from the tab containing the defects or user stories) |
Task Name * | Free text, maximum 1000 characters |
Task Status |
Can include one of the following values: New / In Progress / Completed Default: New |
Task Assignee | An existing user's login name. |
Task Estimated Time(Hours) | Positive integer |
Invested Hours | Positive integer |
Remaining Hours | Positive integer |
Color | To apply a color to the imported task, set the cell's fill color in the cell format. |
Acceptance Tests Sheet
Field * required |
Allowed Values |
---|---|
Backlog Item ID * | The ID of the backlog item relevant to this acceptance test (from the tab containing the defects or user stories) |
Acceptance Tests Description * | Free text, maximum 1000 characters |
Acceptance Test Status |
Can include one of the following values: Not Started / Passed / Failed Default: Not Started |