Can we create parent-child relationships between RRC attributes?
We are working on creating a single RRC project to cater for all upcoming requirements analysis on a very big product (Cúram). We have several functional areas, each of which has a list of categories specific to that functional area that need to be set when creating user stories. I have created a custom attribute called 'functional area' and another custom attribute called 'category'.
I would like to set it up so that when a user selects a particular 'functional area', they then only see the categories specific to that functional area in the category dropdown. To implement this, we need to configure a parent-child relationship between 'functional area' and 'category'.
Could you tell me if this is possible? And if not, if there is an alternative approach I should be using?
Thanks,
Claire
I would like to set it up so that when a user selects a particular 'functional area', they then only see the categories specific to that functional area in the category dropdown. To implement this, we need to configure a parent-child relationship between 'functional area' and 'category'.
Could you tell me if this is possible? And if not, if there is an alternative approach I should be using?
Thanks,
Claire
2 answers
Some people call this "dependent attributes" or "dependent data types", and there is an enhancement request open for it: https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/73175
You are welcome to subscribe and add your voice / use case.
It might be possible to reduce your users' effort by employing one or more JavaScript extensions (but someone would need to write them).
You are welcome to subscribe and add your voice / use case.
It might be possible to reduce your users' effort by employing one or more JavaScript extensions (but someone would need to write them).
Yes.
There is a system defined link type called "decomposition" that has parent-child labels
(System-defined) Captures part-whole relationships between Requirements Management artifacts. These types of links are typically used to represent artifact hierarchies.
You can use this link type to link other requirement artifacts, either in the same project or other projects contained in the same repository.
There is a system defined link type called "decomposition" that has parent-child labels
(System-defined) Captures part-whole relationships between Requirements Management artifacts. These types of links are typically used to represent artifact hierarchies.
You can use this link type to link other requirement artifacts, either in the same project or other projects contained in the same repository.
Comments
Thanks Robin,
Can this link be used to create a parent-child relationship between attributes rather than artifacts? See my comment on the above-mentioned enhancement for further information on what we are trying to achieve: https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=73175