P4DTI issue job000067

TitleWe must say which workflows won't work
Assigned userRichard Brooksby
DescriptionThere are some workflows which just won't work with the replicator. For example, if there's a transition from state A to state A and the user changes something in Perforce, should we apply the transition? This is a special case of the "two transitions from A to B" problematic workflow, and we need to point it out to people in the manual.
Workflows are different for different issue types, so different transitions are available for different issue types. But the ReadTransitionList function only takes a projectid as its parameter. So the replicator can't accurately tell which transitions are valid for the case. API change needed? Document as a limitation.
AnalysisWe have to explain which workflows won't work and how to harmonize workflows in the AG.
See also job000383.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-10-24/teamshare-psg-alpha-test/> item 3
<http://www.ravenbrook.com/project/p4dt...000-11-20/teamshare-alpha-test-meeting/> section 8 item 17
<http://www.ravenbrook.com/project/p4dti/doc/2000-10-24/teamshare-psg-alpha-test/> item 25
Created byRichard Brooksby
Created on2000-11-22 15:02:25
Last modified byGareth Rees
Last modified on2001-12-10 19:03:05
History2000-11-22 RB Created from sources (see evidence)


Change Effect Date User Description
5178 closed 2000-11-30 15:07:42 Richard Brooksby Documenting the TeamTrack workflows that won't work with the replicator.