|Title||There's no way to prevent changes by rules|
|Assigned user||Richard Brooksby|
|Description||Users 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.|
|Analysis||This 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.
|Created by||Richard Brooksby|
|Created on||2000-11-21 15:12:25|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:00:47|
|History||2000-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.
|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.|