P4DTI issue job000043

TitleThere's no way to prevent changes by rules
Assigned userRichard Brooksby
DescriptionUsers would like a way to prevent developers submitting changes (to some branches at certain times) without a fix that links the change to an issue which has a specified priority (requirement 56, requirement 57, requirement 58). For example, only fixes to critical bugs are allowed on the frozen release branch. We don't provide any means to do this.
AnalysisThis can probably be done with some triggers, provided that the information needed to make the decision is replicated into the job from the DT.
See also job000044. This work might be combined with that.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-11-03/quokka-alpha-test/> item 8, inter alia
<http://www.ravenbrook.com/project/p4dti/doc/2000-10-31/mahi-alpha-test/> item 22
Observed in0.3.2
Created byRichard Brooksby
Created on2000-11-21 15:12:25
Last modified byGareth Rees
Last modified on2001-12-10 19:00:47
History2000-11-21 RB Created from sources (see evidence).
2000-11-22 RB Added evidence from Mahi alpha.
2000-12-04 RB Improved description for end users.


Change Effect Date User Description
5580 closed 2000-12-06 22:04:49 Richard Brooksby Removing quotes from P4 arguments in example trigger for compatibility with Windows NT.
5578 open 2000-12-06 21:54:18 Richard Brooksby Adding an example trigger script to enforce extra workflow restrictions in order to meet requirement 56, requirement 57, and requirement 58.