This feature is available in RQM. A defect which is blocking a TER, on resolution will automatically unblock the TER. The condition is customizable as well where in if you have a build system integration with RTC setup, you can chose to unblock the TER when the blocking defect is resolved/closed and the code resolving the defect is included in a build. The customization can be done from the Admin>System Properties.

There is a help topic on the block/unblock automation, which can be found here http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_bld_stat_unblock_tcs.html

We are currently trying the RQM2.0 and RTC2.0 integration feature and have a question related to this integration

If a defect (opened in RTC2.0 or opened in RTC2.0 via RQMv2.0) is associated with a test execution record (ter) in RQM2.0, marking the testcase as failed/blocked, does the integration feature provides ability to dynamically update the testcase status to attempted (or unblock), when the defect changes states (from open --> resolved/fixed)?

RTC2.0 serves a as source repository, user stories/tasks/defects management tool for our product. In the past, we have used CMVC for source repository and TTT as tool for test tracking, where test case status was dynamically updated (via agents) based on status of defects in cmvc. Hence, it is important for us to know if this ability is provided by the integration feature of RQM2.0 and RTC2.0. If not, are there any near term plans to support it?

Thanks for the info. I setup RTC 2.0 & RQM 2.0 servers and the Cross-Server communication is complete. I added a new defect and failed/blocked the Execution Result in RQM. The defect was successfully created on RTC.

I then switched to RTC server, changed this defect status to resolved/closed, is the Execution Result/TER) status in RQM supposed to be changed from Failed/Blocked to 'Attempted'? I did refresh, also tried logout and login again, the status still shows failed or blocked.

My RQM Admin->System Properites -> Execution Preferences has a check mark on 'Unblock the Test Execution Record on closing all the associated defects' (this is default). Any other setting is required?

Also, in RQM, we have to associate/fail 'Execution Result' with either New or Existing defect, why it won't unblock Execution Result but use "unblock the Test Execution Record.." instead ?

The expected behavior is that when the defect gets resolved/closed the TER gets unblocked, ie. the block status field in TER which was earlier showing the blocking icon, now shows an unblocked icon (icon with an empty red circle, a mouse over will also suggest that its unblocked). Periodically, RQM will clean up all the unblocked TER's blocking status and the blocking status column will be empty.

So, either you might be missing out on the change in the icon or you might try to give it certain time to get cleaned up. By default the cleanup happens every ~10 minutes. You can change this as well by going to the ADMIN>jazz server administration>advanced properties page and change the delay property of these services

RQM Change Management Integration>
com.ibm.rqm.defects.service.internal.ChangeRequestCollector

Test Execution Component>
com.ibm.rqm.execution.service.internal.sync.DefectTrackingTask

>Also, in RQM, we have to associate/fail 'Execution Result' with either New or Existing defect, why it won't unblock Execution Result but use "unblock the Test Execution Record.." instead ?
I am not sure if I got this correctly. To explain what blocking a TER means, "a TER is said to be blocked when one cannot proceed with testing this TER unless the defect which is blocking it is resolved."

Thanks for the info. I setup RTC 2.0 & RQM 2.0 servers and the Cross-Server communication is complete. I added a new defect and failed/blocked the Execution Result in RQM. The defect was successfully created on RTC.

I then switched to RTC server, changed this defect status to resolved/closed, is the Execution Result/TER) status in RQM supposed to be changed from Failed/Blocked to 'Attempted'? I did refresh, also tried logout and login again, the status still shows failed or blocked.

My RQM Admin->System Properites -> Execution Preferences has a check mark on 'Unblock the Test Execution Record on closing all the associated defects' (this is default). Any other setting is required?

Also, in RQM, we have to associate/fail 'Execution Result' with either New or Existing defect, why it won't unblock Execution Result but use "unblock the Test Execution Record.." instead ?