It's all about the answers!

Ask a question

alternate option for "dependent enumeration" configuration in RTC


Mohanraj Ragupathi (54520) | asked Feb 15 '18, 8:42 a.m.

 We are using RTC 604.  Management want to introduce Domain wise feature Group in a work Item. Since the user knows which domain they are working, we should show only the feature Group belong to that domain. 


We have a master template which is getting inherited to all our programs irrespective of domain. 

For e.g.  we have domain1, domain 2 and domain3. 
For domain 1 - The feature Groups are---- BlueTooth, Wireless, Widget, Illumination
For domain 2 - The feature Groups are----  Sensor , keypad, Ilumination, Remote
For domain 3 - The feature Groups are---- Widget, Sensor, Voice, Audio, Music

I want to have this domain information some where with in RTC. But can't configure this specifically (as a field) for the programs when it is getting created.

So when the user create a defect for the program, somehow the domain information should be fetched and accordingly the feature group list should be shown in the drop down list. 

I am NOT willing to do project specific XML changes.

Please let me know your ideas.

3 answers



permanent link
Matt Muller (59813674) | answered Feb 15 '18, 9:09 a.m.

Mohanraj,

Are you not using Domain "Teams" or "Sub Teams" or Domain "Categories and / or Sub Categories" to manage this level? 


Comments
Mohanraj Ragupathi commented Feb 16 '18, 1:45 a.m.

As I mentioned in my question, for each workitem for individual programs we need to select. More over this need to be defined at Master Template which will be inherited to the child project areas.

so using "Team"  or "category" will NOT workout in this case.


permanent link
Donald Nong (14.5k414) | answered Feb 21 '18, 1:22 a.m.

If you really have to do it, you can use a script-based value set provider, and within the script use WorkItemAttributes.PROJECT_AREA to determine the "domain".


permanent link
Chandra Prakash k (21214) | answered Feb 21 '18, 7:30 a.m.

 we have tried the below script, but didn't helped us.


dojo.provide("featuregroup.dojo");

dojo.require("com.ibm.team.workitem.api.common.WorkItemAttributes");

(function() {
var WorkItemAttributes= com.ibm.team.workitem.api.common.WorkItemAttributes;

dojo.declare("featuregroup.dojo", null, {

    getValueSet: function(attributeId, workItem, configuration) {
    
        var domain= workItem.getValue(WorkItemAttributes.PROJECT_AREA);
        var functionalblockoptions= [];
        
if ((domain === "xTest-Plugin")) { 
            functionalblockoptions.push("com.visteon.functional.block.literal.l3");
            functionalblockoptions.push("com.visteon.functional.block.literal.l4");
            functionalblockoptions.push("com.visteon.functional.block.literal.l5");
            functionalblockoptions.push("com.visteon.functional.block.literal.l6");
            functionalblockoptions.push("com.visteon.functional.block.literal.l7");
            functionalblockoptions.push("com.visteon.functional.block.literal.l8");
functionalblockoptions.push("com.visteon.functional.block.literal.l9");
            functionalblockoptions.push("com.visteon.functional.block.literal.l10");
}else if((domain === "xTest-Plugin2")) {        
functionalblockoptions.push("com.visteon.functional.block.literal.l11");
functionalblockoptions.push("com.visteon.functional.block.literal.l12");
functionalblockoptions.push("com.visteon.functional.block.literal.l13");
functionalblockoptions.push("com.visteon.functional.block.literal.l14");
functionalblockoptions.push("com.visteon.functional.block.literal.l15");
functionalblockoptions.push("com.visteon.functional.block.literal.l16");
}
functionalblockoptions.push("com.visteon.functional.block.literal.l1");
        return functionalblockoptions;
    }
});
})();

Your answer


Register or to post 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.