| Title | If you run the refresh script as your first step, all issues get overwritten |
| Status | suspended |
| Priority | nice |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If you run the refresh.py script as your first step (before ever running the run.py script) then when you come to run the run.py script all the jobs get overwritten. |
| Analysis | This isn't serious because (1) it does no harm except possibly to confuse people; (2) it's an odd thing to do and (3) it's not what we tell people to do in the AG. |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dt...c/2001-03-05/release-1.0.2-test-report/>, item 7. |
| Observed in | 1.0.2 |
| Introduced in | 0.4.0 |
| Created by | Gareth Rees |
| Created on | 2001-03-05 16:18:04 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:33 |
| History | 2001-03-05 GDR Created. 2001-03-20 RB Guessed "introduced-in" as the release we added "refresh_perforce.py". 2018-07-05 NB Suspended because the P4DTI is obsolete. |