| Title | Illegal transitions should be prevented by Perforce clients |
| Status | suspended |
| Priority | optional |
| Assigned user | Nick Barnes |
| Organization | Perforce |
| Description | Perforce users can make job transitions which are prohibited by the DT workflow. The P4DTI reports and undoes these illegal transitions, but it would be better if the P4 clients did not allow them in the first place. |
| Analysis | This is a defect in Perforce. Some changes to Perforce which would fix it: 1. job-dependent jobspecs. Perforce could support a number of jobspecs, and have one job field specify the jobspec. Then the P4DTI could simply generate a jobspec for each DT issue state, and transition jobs between jobspecs accordingly. 2. A way of specifying data-dependent jobspec restrictions. e.g. "if this field is "foo", this field must be "bar" or "baz". |
| How found | customer |
| Evidence | <URL: http://info.ravenbrook.com/mail/2001/02/06/11-10-20/0.txt> |
| Observed in | 0.4.2 |
| Created by | Nick Barnes |
| Created on | 2001-02-06 16:15:55 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:28 |
| History | 2001-02-06 NB Created. 2001-02-19 GDR Downgraded to optional. 2018-07-05 NB Suspended because the P4DTI is obsolete. |