|Title||Migration to TeamTrack fails unless issue ids are zero-filled to 5 digits|
|Assigned user||Gareth Rees|
|Description||If you change the number of digits to which issue ids are zero-filled, migration and replication of new issues doesn't work.|
|Analysis||This is because the TSServer::Submit method doesn't return the ID of the new issue, but rather the ISSUEID, as a number. To find the ID of that issue we need to search the CASES table for a record with the given ISSUEID. But ISSUEIDs in the database are strings, zero-filled to some number of digits. Since 5 is the default number of digits to fill to, the P4DTI looks for that -- but it may end up looking for ISSUEID='00123' when it should be looking for ISSUEID='000123' or whatever.|
1. Read the number of zero-fill digits for the project to which we submitted the issue. It's the ZEROFILLTO field in the PROJECTS table.
2. Get the newly-created issue in a different way; perhaps by TS_ID=(SELECT MAX(TS_ID) FROM TS_CASES WHERE TS_ISSUEID LIKE '%123'); this might work because new issues get added to the end of the table. Unfortunately there is a race condition: if BUG01123 and ENH00123 get submitted in the same poll period then we might pick the wrong one.
3. Ask TeamShare to improve the API so that new issues can be reliably identified.
|Created by||Gareth Rees|
|Created on||2001-12-03 19:40:23|
|Last modified by||Gareth Rees|
|Last modified on||2002-01-10 16:04:28|
|History||2001-12-03 GDR Created.|
|25786||closed||2002-01-10 17:11:25||Gareth Rees||Fixed TeamTrack integration so that migration of issues to TeamTrack works regardless of how issueids are represented. Added test case.
The TeamTrack 4.5 integration doesn't support migration or creation of new issues in Perforce.