Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues
Perforce Defect Tracking Integration
| Title: | Refresh script fails if you change the closed_state |
| Status: | closed |
| Priority: | essential |
| Assigned user: | gdr |
| Product: | p4dti |
| Organization: | Ravenbrook |
| Description: | Suppose 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). |
| Analysis: | The 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 found: | manual_test |
| Evidence: | <http://www.ravenbrook.com/project/p4dti/doc/2001-03-05/release-1.0.2-test-report/>, item 6. |
| Observed in: | 1.0.2 |
| Introduced in: | 0.4.0 |
| Test procedure: | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 17 |
| Created by: | gdr |
| Created on: | 2001-03-05 16:15:24 |
| Last modified by: | gdr |
| Last modified on: | 2001-12-10 19:30:11 |
| History: | 2001-03-05 GDR Created. 2001-07-17 GDR Added analysis. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 24539 | closed | 2001-11-28 21:15:41 | gdr | 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. |
Generated at 2008-10-14 19:50:44 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#430 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.