| Title | Fixes not replicated until another change is made |
| Status | suspended |
| Priority | optional |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | When we added a fix to a job, the replicator doesn't actually manage to replicate the fix until or unless you change a field in the job. We've not been able to reproduce this problem since alpha testing, and it only occurred at one site. |
| Analysis | Is the fix being added to the database but with the wrong RECID or something like that? |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-10-27/perforce-alpha-test/> item 6 |
| Observed in | 0.3.2 |
| Created by | Richard Brooksby |
| Created on | 2000-11-22 13:04:41 |
| Last modified by | Gareth Rees |
| Last modified on | 2002-01-09 15:08:11 |
| History | 2000-11-22 RB Created from sources (see evidence). 2000-12-04 RB Improved description for end users. Downgraded from "essential" to "optional" because we haven't seen it again. 2001-01-09 GDR No further report for over a year, so suspended. |