Mapping Fields Without a Solution Map

If you do not specify a converted solution when you import data from a Tracker database, you must manually map Tracker fields to SBM fields. Consider the following information when you map fields without specifying a solution converted from a Tracker project:

• When you map the first User or Multi-User field in the SBM Field column, the Options: How to Map Field Values dialog box opens. You can then define user mapping that applies to data in all User and Multi-User fields you import with this Import Option Set. For details, refer to Mapping Field Values for Selection and User Fields.

• When you map each Single Selection and Multi-Selection field in the SBM Field column, the Options: How to Map Field Values dialog box opens. You can then define selection mapping for the field.

• If you want to establish ownership based a Tracker field, map this field to the Owner field. Because values in the Owner field change as users transition items through a workflow, also map the source field to another User field in the receiving database so that data is retained.

• If you do not map to the Issue ID field, imported items are assigned new issue IDs by default. To maintain historic item IDs, you can map the Issue ID field to a Tracker ID field, but doing so may result in duplicate issue IDs in SBM. One option for maintaining legacy Item IDs is to create a field in the receiving database to map the Tracker issue ID field to.

• The Issue Type field uses three-letter prefixes that are prepended to the Issue ID. For example, a defect might have an Issue ID of DEF00011 and an enhancement might have an Issue ID of ENH00025. If you did not import Item Type selections when you ran the Solution Wizard, you can do so when you import data using the Import Data Wizard. Note, however, that Issue Type prefixes are only automatically created using the Solution Wizard and must be manually created if you import Issue Type selections using the Import Data Wizard.