RQM 4 : Requirement Collection with DOORS

Oh, I think the problem is solved.

There was a wrong link in the Doors module configuration.
It was set to port 8080 instead of the used DWA port.

greetings georg.

Hi Damien,

Are you using the OSLC-style of RQM/DOORS integration?  If so, are you using the OSLC QM V2 API or the RQM UI to add the requirement collection to the test plan? 

Paul

Hi Paul,

Ye we are using the RQM/DOORS Integration and the RQM UI to add a DOORS Standard View to the test plan.

Damien

If you are following the correct steps, it may be a configuration issue.  Can you check your configuration?

We have checked the configuration. All seems correct. What can we do now ? logfiles ?
Thanks for your help

Could you please open a new RQM defect and attach your RQM logs?

Hi Damien,
There are several possibilites before determining whether it is a defect.

1. Are you seeing the alert when you trying to create a collection for a test plan? DOORs does not support creation collection from RQM.

2. Are you able to see the selection dialog but failed after select a module/view? if so, do your module/view contains special characters? there is a known defect on DOORs side, they did not encode the special character before sending to RQM, which causes xml parser fails, and we have a defect tracking this problem for providing a better message: Should expose more information when there are "Not Supported" characters in requirement link url (74299)

If none of the above, are you able to add requirement links to test case? are you able to add test case link from DOORs side? which browser (and version) are you using?

Thanks,
Scarlett
RQM Dev Team

I am trying to link Test plan to the Module, all goes well and I select the Module and click Okay.
However after clicking Ok in module selection dialog, nothing shows up in the "Requirement Collection Links" section. Also Save button remains disabled
I am using CLM v401 and DOORS 9.5

Any news regarding this issue?
We're facing the same problem.

Arti, Georg - are you seeing any exceptions in qm.log or DOORs logs? or some web ui errors in the firebug console?

If you don't mind, we can create a defect to attach logs and track the problem.

Thanks,

Scarlett