ODC in RTC
Is there a best practice way yet of extending the defect work item in RTC to implement ODC?
|
4 answers
johnmatt@ie.ibm-dot-com.no-spam.invalid (johnmatt) wrote in news:h7gv5c$3un
$1@localhost.localdomain: Is there a best practice way yet of extending the defect work item in We did create our own flow, attributes and type to 'mimic' the IBM standard. We did not formally implement ODC, but we did extend the type to add causal analysis. Let me know if you want to know more about it... -- Christophe Elek Jazz L3 IBM Software Group - Rational |
|
Yes Christopher. I would be interested in what you did; perhaps you could email me or post details here.
Do you know of any plans to implement this IBM standard into the product? johnmatt@ie.ibm-dot-com.no-spam.invalid (johnmatt) wrote in news:h7gv5c$3un Is there a best practice way yet of extending the defect work item in We did create our own flow, attributes and type to 'mimic' the IBM standard. We did not formally implement ODC, but we did extend the type to add causal analysis. Let me know if you want to know more about it... -- Christophe Elek Jazz L3 IBM Software Group - Rational |
Christophe, did you manage to reflect relatations between respective ODC fields? For example if one chooses an ODC_Activity, ODC_Trigger gets filtered out, so only options assign to a chosen ODC_Activity are available.
|
|
There are so called "Work Item Attribute Value Providers" introduced in RTC 2.0.0.2. These value providers may be used to reflect dependecies between respective ODC fields.
https://jazz.net/wiki/bin/view/Main/AttributeValueProviders |
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.