| Title | There's no documented way to prevent a transition without a fix |
| Status | suspended |
| Priority | nice |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | Users would like to prevent issues transitioning [sic] to certain states unless there's a fix that links the issue to a change. |
| Analysis | This can probably be enforced with rules in the DT's workflow, provided that it can reference the fixes data. See also job000043. This work might be combined with that. GDR 2001-07-17: In Bugzilla you'd have to hack the transition rules,in TeamTrack you'd write a trigger in their extension language. All the data is there. |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-11-03/quokka-alpha-test/> item 8, inter alia |
| Observed in | 0.3.2 |
| Created by | Richard Brooksby |
| Created on | 2000-11-21 15:14:06 |
| Last modified by | Richard Brooksby |
| Last modified on | 2013-03-15 12:19:41 |
| History | 2000-11-21 RB Created from sources (see evidence) 2001-07-17 GDR Downgraded to nice, added analysis. 2013-03-15 RB Suspended ancient job in defunct project. |