Welcome to the Jazz Community Forum
Setting the "Assigned to" Field to Unassigned
The example is that in one state the value is a developer and then in the next state it needs to be changed to a tester, but it is still populated, so even though the field is required, it can overlook being reset to a tester's name. If it was cleared to Unassigned, then it would error out if attempted to be saved without being set.
2 answers
there was a discussion at one point about possibly ordering the advisors and participants in such an order as to maybe enable this.. but if a participant does an explicit Save, it drives another advisor chain invocation, which will eventually reach the required field advisor who will reject the save..
Comments
I want it to be unassigned (cleared out) when it enters the state (like a precondition) but must be valued upon save (required). The point is to force them to choose a username each time the state is entered. I did this easily and often in ClearQuest.
Ok, so you want an field on change handler to be able force ANOTHER field to unassigned when they click to change the state... .
I do not know if the JS handlers run AT the field click level (onchange)..
It is my understanding that only the "required" and "read-only" JS handlers run at field-click level time, while all the other JS handlers (and the pre/post conditions) only run at save/commit time (and therefore are not of use to you for this functionality). In contrast, ClearQuest does let you define arbitrary field-commit hook code, so to my knowledge, you can do this kind of customization in ClearQuest but not in RTC.
1 vote
