P4DTI issue job000310

TitleTeamTrack 5.0 is not supported
Assigned userGareth Rees
DescriptionThe P4DTI doesn't support TeamTrack 5.0. This means that P4DTI customers won't be able to upgrade their TeamTrack server when TeamShare release TeamTrack 5.
AnalysisIt's not supported because TeamTrack 5 has not been released. It is essential that the P4DTI support TeamTrack 5 when it is released.
We have tested it against the beta release (build 5024C) [2].
We tried using the TeamShare API from buid 4509. This doesn't work: the method ReadRecordListWithWhere() returns at most a single record when connecting to a 5.0 server, regardless of how many records match the query. [3]
GDR 2001-05-19: TeamShare sent us a new API [4]. This doesn't work. It doesn't fetch records from TS_ISSUES and TS_FIELDS tables (it fetches records from all other tables).
There are incompatibilities in the database schema [5], for example the TS_CASES table is now called TS_ISSUES. There are two possible approaches to these incompatibilities: support both 4.5 and 5.0 in one integration (with switches in appropriate places); or have two integrations, one for 4.5 and one for 5.0.
GDR 2001-06-07: See job000326 for a major problem we've found with TeamTrack 5.0. TeamShare sent us another API release [6].
GDR 2001-06-21: This is Perforce's job 5900.
GDR 2001-06-28: See [7] and [8] if we need to tell people where to get TeamTrack 4.5.
How foundinspection
Evidence[1] <http://info.ravenbrook.com/mail/2001/04/30/12-12-46/0.txt>
[2] <http://www.ravenbrook.com/project/p4dti/import/2001-04-30/teamtrack-5-beta/>
[3] <http://info.ravenbrook.com/mail/2001/05/15/14-35-45/0.txt>
[4] <http://www.ravenbrook.com/project/p4dti/import/2001-04-30/teamtrack-5-beta/api/>
[5] <http://info.ravenbrook.com/project/p4d...-04-30/teamtrack-schema-5.0/schema.html>
[6] <http://www.ravenbrook.com/project/p4dti/import/2001-06-06/teamshare-api/>
[7] <http://info.ravenbrook.com/mail/2001/06/27/00-09-20/0.txt>
[8] <http://info.ravenbrook.com/mail/2001/06/27/16-07-33/0.txt>
Observed in1.1.1
Created byGareth Rees
Created on2001-04-30 13:26:15
Last modified byGareth Rees
Last modified on2001-12-10 19:41:54
History2001-04-30 GDR Created.
2001-05-01 GDR Added analysis in response to Kersti Hale.
2001-05-15 NDL Added analysis in the light of initial testing.
2001-05-19 GDR Analysis of using new API.
2001-06-21 GDR Added reference to Perforce job 5900.
2001-06-28 GDR Added note about downloading TeamTrack 4.5.


Change Effect Date User Description
13767 closed 2001-07-03 12:36:09 Gareth Rees Added support for TeamTrack 5.0:
Split code/tsapi/... into code/tsapi-4.5/... and code/tsapi-5.0/... and split the Developer Studio project teamtrack.dsp into teamtrack-4.5.dsp and teamtrack-5.0.dspso that I can build two copies of the Python interface to TeamTrack, one for TeamTrack 4.5 and one for TeamTrack 5.0.
Updated teamtrack-module.cpp so that it has two entry points (one for each module).
Added teamtrack_version configuration parameter.
Updated design, Administrator Guide and release notes.