RQM-RTC Integration - entering RTC Defects from RQM
Hi everyone,
I have setup the RQM-RTC integration and when I hover above the Defects icon (in the RQM Web interface) I see three choices.
1. Create Defect in the RTC Project
2. Goto Defects in the RTC Project
3. Goto Workitems in RQM
When I get the pop-up to Create the Defect only a few of my fields appear. How do I customize that so that it actually matches the Defects that I have in RTC?
Also is there anyway to hide option #3. I have users who are putting Defects into the local RQM when they really wanted them to be in RTC.
Any help would be greatly appreciated!
Bob Aiello
http://www.linkedin.com/in/BobAiello
I have setup the RQM-RTC integration and when I hover above the Defects icon (in the RQM Web interface) I see three choices.
1. Create Defect in the RTC Project
2. Goto Defects in the RTC Project
3. Goto Workitems in RQM
When I get the pop-up to Create the Defect only a few of my fields appear. How do I customize that so that it actually matches the Defects that I have in RTC?
Also is there anyway to hide option #3. I have users who are putting Defects into the local RQM when they really wanted them to be in RTC.
Any help would be greatly appreciated!
Bob Aiello
http://www.linkedin.com/in/BobAiello
2 answers
Hi everyone,
Also is there anyway to hide option #3. I have users who are putting Defects into the local RQM when they really wanted them to be in RTC.
Any help would be greatly appreciated!
Hi Bob
I was also a bit puzzled that although I'd integrated RQM and RTC, users were still able to follow the Goto Workitems link and then create defects directly into RQM (rather than into RTC).
So what I have just tried (and it seems to work fine) is
1. pointed my RTC Eclipse client at my RQM instance,
2. opened up my RQM project area,
3. go to the process configuration source of the project area,
4. Commented out the following....
<!-- Remove ability to create defects directly into RQM as they are created in RTC
<type category="com.ibm.team.workitem.workItemType"
dimmedicon="platform:/plugin/com.ibm.team.workitem.common/icons/obj16/wi_bug_dim.gif"
icon="platform:/plugin/com.ibm.team.workitem.common/icons/obj16/wi_bug.gif"
id="defect" name="Defect">
<alias name="bug"/>
</type>
-->
This means that users can no longer create defects directly in RQM.
I've only run a cursory test but this seems to work fine.
Hope that helps.
Greg
We have our RQM 2.0.1 ifix3 server integrated with our RTC 2.0.02 server, so that we can raise defects in RTC.
If we create a blocking defect from RQM, the test case will remain in a blocked state until the developer/tester fixes the problem and resolves the defect on RTC.
Once resolved, a task runs periodically on RTC or RQM (not sure which), to communicate with the RQM server to unblock the test case.
What is this task ? where does it run ? and can I change the frequency, it seems to run about once a day.
Thanks
D
If we create a blocking defect from RQM, the test case will remain in a blocked state until the developer/tester fixes the problem and resolves the defect on RTC.
Once resolved, a task runs periodically on RTC or RQM (not sure which), to communicate with the RQM server to unblock the test case.
What is this task ? where does it run ? and can I change the frequency, it seems to run about once a day.
Thanks
D