P4DTI issue job000159

TitleFixes which the replicator rejects still get replicated
Assigned userNick Barnes
DescriptionIf a Perforce user makes a fix which the defect tracker disallows for some reason (e.g. it's an illegal transition in the defect tracker, the user doesn't have the necessary permissions to make the transition, etc), then the replicator will correctly refuse to replicate the change to the issue's status and will undo the change to the job's status, in accordance with the "defect tracker wins" policy.
However, the fix record itself will be replicated, and will show up in the defect tracker's interface. This is misleading. Better behaviour would be for the replicator to remove the fix (and not replicate it).
AnalysisRichard says this is hard.
This is a duplicate of job000137. GDR 2000-12-30
See also <http://www.ravenbrook.com/project/p4dt...2001-02-22/version-1.0-support/#job-159>.
How foundmanual_test
EvidenceNoted when testing 0.5.0.
Observed in0.5.0
Created byNick Barnes
Created on2000-12-15 14:50:28
Last modified byGareth Rees
Last modified on2001-12-10 19:15:33
History2000-12-15 NB Created.
2000-12-30 GDR Closed (duplicate of job000137).
2001-02-19 GDR Downgraded to essential.


Change Effect Date User Description
22485 closed 2001-09-14 13:09:54 Gareth Rees Added section explaining how the P4DTI enforces the defect tracker's rules. Explained why fixes aren't deleted even if they cause an illegal change.