|Title||We must say which workflows won't work|
|Assigned user||Richard Brooksby|
|Description||There 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.
|Analysis||We have to explain which workflows won't work and how to harmonize workflows in the AG.|
See also job000383.
|Created by||Richard Brooksby|
|Created on||2000-11-22 15:02:25|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:03:05|
|History||2000-11-22 RB Created from sources (see evidence)|
|5178||closed||2000-11-30 15:07:42||Richard Brooksby||Documenting the TeamTrack workflows that won't work with the replicator.|