P4DTI issue job000249

TitleRefresh script fails if you change the closed_state
Assigned userGareth Rees
DescriptionSuppose you start out with closed_state=None and people make fixes in Perforce to the state "resolved". Then you set closed_state="resolved" and run the refresh script. This fails because it tries to make fixes to the state "resolved", which Perforce refuses because there is no Perforce state "resolved" (Perforce now uses "closed" instead).
AnalysisThe configuration generator could look at the fix "effects" in the defect tracker and make sure all of these are available as legal states in Perforce.
Or we could translate the fix effect when we replicate it to the defect tracker.
GDR 2001-07-17: Or we could tell people to go into their database and change all this stuff by hand (or say "call support"). But in TeamTrack it's not so simple because of the way fixes are packed into structures. We could have a script that changes a status in the fixes table in the defect tracker.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dt...c/2001-03-05/release-1.0.2-test-report/>, item 6.
Observed in1.0.2
Introduced in0.4.0
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 17
Created byGareth Rees
Created on2001-03-05 16:15:24
Last modified byGareth Rees
Last modified on2001-12-10 19:30:11
History2001-03-05 GDR Created.
2001-07-17 GDR Added analysis.


Change Effect Date User Description
24539 closed 2001-11-28 21:15:41 Gareth Rees Don't delete jobs when refreshing, just update them. This avoids deleting fixes, and so prevents problems arising from fixes with old or otherwise invalid statuses.