| Title | TeamTrack integration doesn't support primary tables other than TS_CASES/TTT_ISSUES |
| Status | suspended |
| Priority | nice |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | Some TeamShare customers use tables other than TS_CASES and TTT_ISSUES to put their defects in. They can select exactly which fields to include in their table of defects, and which defects go where. This improves performance. However, the P4DTI only support TS_CASES or TTT_ISSUES. The P4DTI TeamTrack integration is now maintained and supported by TeamShare <http://www.teamshare.com/>. |
| Analysis | The P4DTI administrator would specify a list of tables to be replicated. We'd have to work out a Perforce jobspec that contained each field from each table to be replicated, and make replication field maps for each such table. This seems like a configuration nightmare, but maybe it could be made to work. (Or we could restrict what we support to a single primary table.) |
| How found | customer |
| Evidence | <http://info.ravenbrook.com/mail/2001/07/24/19-34-22/0.txt>, item 1. |
| Observed in | 1.1.3 |
| Introduced in | 1.1.2 |
| Created by | Gareth Rees |
| Created on | 2001-07-24 22:22:44 |
| Last modified by | David Jones |
| Last modified on | 2003-08-19 13:55:18 |
| History | 2001-07-24 GDR Created. 2003-05-19 NB TeamShare handover. 2003-08-19 DRJ Suspended due to teamshare handover |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 35521 | suspended | 2002-11-14 13:44:46 | Richard Brooksby | Removing TeamTrack support from master sources. Updating project index and FAQ to reflect new TeamTrack situation. |