Setting the "Assigned to" Field to Unassigned
Barb Oxenford (23●11●13)
| asked Mar 29 '13, 10:16 a.m.
edited Mar 29 '13, 10:50 a.m. by Ralph Schoon (63.1k●3●36●46)
Has anyone implemented the "Assigned to" field becoming Unassigned when there is a State change that makes it Required?
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
Ralph Schoon (63.1k●3●36●46)
| answered Mar 29 '13, 2:16 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As far as I can tell Sam is completely right. Despite the fact of http://rsjazz.wordpress.com/2012/12/14/do-not-modify-the-triggering-element-in-an-operationadvisor/
I agree that you can not do this, except you make the attribute not required by the standard settings and add you own advisor and use the additional parameters as in
http://rsjazz.wordpress.com/2012/07/31/rtc-update-parent-duration-estimation-and-effort-participant/ to communicate the ax caption.
Comments And add a participant hat changes the owner.
I personally would do otherwise and spawn a new task for the quality control guy, or add an additional contributor attribute for the QM guy.
|
you cannot set a required field to unassigned, even in a participant. the save will be rejected.
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... .
1
Geoffrey Clemm
commented Apr 02 '13, 6:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.