| Title | The migrate script loses fixes |
| Status | closed |
| Priority | essential |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | If you follow the migration procedure in section 6.2 of the Administrator's Guide, then you lose all the fixes in Perforce. |
| Analysis | The migrate_teamtrack.py script doesn't replicate the fixes. |
| How found | inspection |
| Evidence | <http://www.ravenbrook.com/project/p4dt....0/code/replicator/migrate_teamtrack.py> |
| Observed in | 1.0.5 |
| Introduced in | 1.0.0 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 17 |
| Created by | Gareth Rees |
| Created on | 2001-03-22 08:09:14 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:34:47 |
| History | 2001-03-22 GDR Created. 2001-03-25 RB Change 10577 removes the script, so downgraded this to essential. We still need to provide migration. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 14147 | closed | 2001-07-15 19:43:44 | Gareth Rees | Removed migration script and migration instructions. |
| 10579 | open | 2001-03-25 11:34:56 | Gareth Rees | Tell people to replicate fixes as well as jobs in section 6.2. |
| 10577 | open | 2001-03-25 11:24:40 | Richard Brooksby | Quick fix: 1. Cutting the details from AG 6.2 which describes how to migrate. 2. Removing the non-working migration script so that people won't try it. |
| 10467 | open | 2001-03-23 08:40:56 | Gareth Rees | The Perforce to TeamTrack migration script now migrates fixes as well as jobs. |