P4DTI issue job000062

TitleFixes not replicated until another change is made
Statussuspended
Priorityoptional
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionWhen 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.
AnalysisIs the fix being added to the database but with the wrong RECID or something like that?
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-10-27/perforce-alpha-test/> item 6
Observed in0.3.2
Created byRichard Brooksby
Created on2000-11-22 13:04:41
Last modified byGareth Rees
Last modified on2002-01-09 15:08:11
History2000-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.