Although not the same thing, I post this request (from Joachim Flammer/CERN) to this task since it could be part of a general enhancement of the transition control mechanism:
Is there a way to put enforcement on state transitions (e.g. for moving a patch to release to have all the associated bugs in a certain state, or to have some fields required to be filled from a certain state on but not in general)?
This is definitely more complex since it constraints a transition to the state of other items.
Yves

This item has been reassigned from the project Savane support tracker to your tracker.

The original report is still available at support #1262

Following are the information included in the original report:

[field #0] Item ID: 1262
[field #1] Group ID: 116
[field #2] Open/Closed: Open
[field #3] Severity: 3 - Normal
[field #4] Privacy: Public
[field #6] Category: Feature Request
[field #7] Submitted by: ype
[field #8] Assigned to: None
[field #9] Submitted on: jeudi 14.09.2006 à 10:08
[field #10] Summary: constraining Open/Closed transitions in a given Status value
[field #11] Original Submission: CERN LCG Savannah sr #101191:
Hello,

I d like to forbid transitions to Open/Closed when an item is in a given status, perhaps something like a "lock" feature in the drop-box list of the "Other fields to update..." page.
This is actually a more general enhancement which would allow to better control a formal workflow, namely:

if(fieldX.value == foo ) {
fieldY.value = bar ;
...
fieldY.lock();
...
}

Cheers,

Marco E.
[field #13] Item Group: None
[field #14] Status: None
[field #15] Component Version: None
[field #16] Operating System: None
[field #17] Reproducibility: None
[field #18] Size (loc): None
[field #19] Fixed Release: None
[field #20] Planned Release: None
[field #21] Effort: 0.00
[field #25] Priority: 5 - Normal
[field #28] Percent Complete: 0%
[field #30] Release: None
[field #55] Custom Select Box #1: None
[field #56] Custom Select Box #2: None
[field #57] Custom Select Box #3: None
[field #58] Custom Select Box #4: None
[field #59] Custom Select Box #5: None
[field #60] Custom Select Box #6: None
[field #61] Custom Select Box #7: None
[field #62] Custom Select Box #8: None
[field #63] Custom Select Box #9: None
[field #64] Custom Select Box #10: None

CERN LCG Savannah sr #101191:
Hello,

I'd like to forbid transitions to Open/Closed when an item is in a given status, perhaps something like a "lock" feature in the drop-box list of the "Other fields to update..." page.
This is actually a more general enhancement which would allow to better control a formal workflow, namely:

if(fieldX.value == 'foo') {
fieldY.value = 'bar';
...
fieldY.lock();
...
}

Cheers,

Marco E.