Dependent attributes (fields): behavior / data dependency
Is there any way in RTC to manage "dependent attributes"? Or plans for it?
Basically I am trying to accomplish the following things:
1) From behavior perspective: make an attribute mandatory -or not- dependent on another attribute's value.
2) From data perspective: having a calculated field based on other attribute's values.
Any answer and/or guidance would be appreciated.
Thanks
Claudia
Basically I am trying to accomplish the following things:
1) From behavior perspective: make an attribute mandatory -or not- dependent on another attribute's value.
2) From data perspective: having a calculated field based on other attribute's values.
Any answer and/or guidance would be appreciated.
Thanks
Claudia
2 answers
On Mon, 13 Apr 2009 19:47:58 +0000, ccalleg wrote:
I'm not super familiar with the Work Item APIs, but this certainly sounds
possible.
--
Jared Burns
Jazz Process Team
1) From behavior perspective: make an attribute mandatory -or not-
dependent on another attribute's value.
2) From data perspective: having a calculated field based on other
attribute's values.
I'm not super familiar with the Work Item APIs, but this certainly sounds
possible.
--
Jared Burns
Jazz Process Team
Is there any way in RTC to manage "dependent attributes"? Or
plans for it?
Basically I am trying to accomplish the following things:
1) From behavior perspective: make an attribute mandatory -or not-
dependent on another attribute's value.
2) From data perspective: having a calculated field based on other
attribute's values.
Any answer and/or guidance would be appreciated.
Thanks
I have added a new Wiki topic that explains how you could implement this
now:
https://jazz.net/wiki/bin/view/Main/CalculatedAttributePresentation
The real request is tracked in
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/92844
--
Regards,
Patrick
Jazz Work Item Team