Download SpiraTest External Bug Tracking Integration Guide

Once you have found the matching Area (by name), the numeric value stored in the ID column (the one
on the left) is the value that needs to get added as the External Key inside SpiraTeam.
b) TFS Custom Fields
If the custom field in TFS is a list field, first you need to go to Administration > Edit Custom Lists in
SpiraTeam and create a new custom list that contains all the different values that are being used in TFS.
Then for both list-fields and value-fields you need to go to Administration > Edit Custom Properties and
add a new custom property onto the Task artifact type with the name of the appropriate TFS field (e.g.
Discipline, Stack Rank, etc.) and if a list-field, link it to the custom list you created in the previous step.
The custom property will now be available for data-mapping.
Now, back in the data-synchronization data-mapping page, click on the hyperlink under Task Custom
Properties that corresponds to the custom property to bring up the custom property mapping configuration
screen:
First you need to enter the full Reference Name of the TFS field as the External Key of the custom
property. This tells the data-sync plug-in that the custom property in SpiraTeam should be mapped to this
specific field in TFS. To see a list of fields and their reference names, you can run the following SQL
query against your TFS database:
SELECT Name, ReferenceName FROM Fields ORDER BY Name
We have included a list of fields in the Agile process template in section 5.5 of this guide as a helpful
reference.
Next for each of the Property Values in the table (in the lower half of the page) you need to enter the
name of the field values as they appear in TFS as the External Key.
© Copyright 2006-2015, Inflectra Corporation
Page 68 of 168
This document contains Inflectra proprietary information