Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Unable to import requirements from ReqPro to RQM

Questions
Tags
Users
Badges
Rajesh Avanthi
(108●15●145●173) retagged
Jan 16 '13, 8:27 a.m.
Rational Quality Manager - Standard Edition 2.0.1
Requisite-pro v7.1.2

We have created a few requirements under Requisite-pro with requirement type set to default type named "Application Requirement".
Clicked on "Requirements" >> "Import Requirements" to get the requirements from ReqPro.
Unfortunately during the process of importing the requirements into RQM, it says importing one requirement.
Lastly it prompts that " Zero requirements  are successfully imported".

We have logged in with a user having Jazz admin privileges. Fortunately when we are able to import the same requirements into another similar  QM project area successfully.
So is there any specific permissions / settings that I need to check on this specific QM project area so that the requirments are imported successfully?

Additional Note:   The synchronization is also enabled for the concerned QM project area.

Any inputs please?

Thanks




0 votes

Comments
Rajesh Avanthi
Jan 16 '13, 11:45 p.m.
So my question is will things stop working if you modify the RequisitePro project structure, as was done here where the Project Name was changed and a new Attribute was added to a Requirement Type.  RQM seems to be very sensitive to this, and that may be what is causing the problems. Earlier when the import was working fine, the RequisitePro Project Name was "BreeZE." Imports from RequisitePro into the "BreeZE" Project Area in RQM were working. Later the name of the RequisitePro project was changed from "BreeZE" to "DCA_BreEZe_Project", and then changed again the same day to "DCA BreEZe Project".  In addition, the RequisitePro Requirement Type "CON" was modified .  A new Attribute was added to it named "Impacted Boards.

Rajesh Avanthi
Jan 18 '13, 5:26 a.m.
Any inputs please ? Additional info:  =========== When verified the "schemaname.RqProjects" table under ReqPro, we notice the renamed ReqPro project name. Initially, I thought that the ReqPro project name might have not changed in the underlying table and might be causing the odd behavior. However from the same ReqPro project, we are able to import the requirements into other RQM project areas and not the one specific.

1 answer
7,775 views
0 votes

One answer

Permanent link
Lei Shi
(227●1) Mar 05 '13, 9:57 p.m.
RQM 201 don't support the rename of ReqPro, and you can try to change the name back to the old one and have a try.

0 votes

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,144
× 7,622

Question asked: Jan 16 '13, 7:11 a.m.

Question was seen: 7,775 times

Last updated: Mar 05 '13, 9:57 p.m.

Confirmation Cancel Confirm