Download SpiraTest External Bug Tracking Integration Guide

match which equivalent user in OnTime. Click [Update] once you’ve entered the appropriate login name.
You should now repeat for the other users who will be active in both systems.
12.2.3. Configuring the Release Mapping
When the data-synchronization service runs, when it comes across a release/iteration in SpiraTeam that it
has not seen before, it will create a corresponding Release in OnTime. Similarly if it comes across a new
Release in OnTime that it has not seen before, it will create a new Release in SpiraTeam. Therefore
when using both systems together, it is recommended that you only enter new Releases in one system
and let the data-synchronization service add them to the other system.
However you may start out with the situation where you already have pre-existing Releases in both
systems that you need to associate in the data-mapping. If you don’t do this, you may find that duplicates
get created when you first enable the data-synchronization service. Therefore for any Releases/Iterations
that already exist in BOTH systems please navigate to Planning > Releases and click on the
Release/Iteration in question. Make sure you have the ‘Overview’ tab visible and expand the “Details”
section of the release/iteration:
In addition to the standard fields and custom properties configured for Releases, you will see an
additional text property called “OnTimeDataSync ID” that is used to store the mapped external identifier
for the equivalent Version in OnTime. You need to locate the ID of the equivalent version in OnTime,
enter it into this text-box and click [Save]. You should now repeat for all the other pre-existing releases.
Note: The OnTime ID can be found by looking at the URL inside OnTime when choosing to Edit the
release in question. The URL will include the section: ReleaseId=X where X is the numeric ID of the
version inside OnTime:
© Copyright 2006-2015, Inflectra Corporation
Page 158 of 168
This document contains Inflectra proprietary information