| Title | Can't fix (and then delete the fix) a job owned by user (None) in the TeamTrack integration |
| Status | closed |
| Priority | optional |
| Assigned user | Gareth Rees |
| Organization | Perforce |
| Description | If an issue has no owner in TeamTrack (and therefore the owner of the corresponding job is (None) in Perforce) then you can't transition the job by fixing and then immediately delete the fix. The replicator is unable to replicate the change to the job and it overwrites the job with the issue. |
| Analysis | This has the same underlying cause as job000016, job000042, job000086, job000133, and job000270. This is really just a side case of job000270: see the analysis for that job. |
| How found | inspection |
| Evidence | See job000270. |
| Observed in | 1.0.5 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 21 |
| Created by | Gareth Rees |
| Created on | 2001-03-23 14:39:39 |
| Last modified by | Gareth Rees |
| Last modified on | 2002-01-28 18:19:55 |
| History | 2001-03-23 GDR Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 26176 | closed | 2002-01-28 20:50:48 | Gareth Rees | Don't replicate changes in Perforce that we made in the previous poll. Perforce interface records server changelevel. In Perforce 2002.1, use the P4DTI-user field as an accurate guide as to who last edited the job. |