It's all about the answers!

Ask a question

How to create Artifact Type and New Requirement in Rational Quality Management 4.0 (CRRRW7321W)


Gaetano Siano (1311013) | asked May 22 '13, 4:30 a.m.
edited May 22 '13, 4:42 a.m.
 I cannot create test requirements in my BizPlates RQM project due to permissions.  I have added User TANO to the administrators tab and have given him all the roles in the Members section. I have also given all the Roles every possible permission but i still get the error below.  I have not defined any timelines or iterations. Does this matter?  Access control is set to "Grant read access to everyone"

ID CRRRW7321W Artifact types are not defined in this project. Artifact types are required for creating artifacts. You can create artifact types on the administrator page. To create artifact types you must have the save type permission for the project.

The funny thing is that i can create requirements in another RQM lifecycle project and i have copied the same persmissions across.  Can anyone help me out here? 
Thanks



4 answers



permanent link
Anthony Kesterton (7.5k9180136) | answered May 22 '13, 5:22 a.m.
JAZZ DEVELOPER
Can you go to your RRC project you have connected to RQM, and see if there are any reqirement types.  It is possible you don't have any requirement types set up in the RRC project. Look at the RRC project properties (via the admin menu once you have a RRC page open.

If you don't have types, you should be able to create some from this project properties page.

anthony

permanent link
Gaetano Siano (1311013) | answered May 22 '13, 8:20 p.m.
 Hi, i dont have requisite pro or RRC or source control or defect tracking . Its just a server running RQM only.

In one project i have managed to add requirements via the Requirements Management project without running any external addon (plugin). But that was a long time ago and i cant recall what i did differently. Both Requirements Management projects look identical except my new BizPlates Requirements Management project wont add requirements.

Comments
Anthony Kesterton commented May 23 '13, 10:23 a.m. | edited unknown
JAZZ DEVELOPER

Hi

I am running 4.0.2 - so may be seeing slightly different behaviour.  In my setup, I need to have another tool linked in to handle requirements with RQM.  You used to be able to have requirements in RQM directly (without any other requirements tool connected) - but this does not appear to be the case any longer.

As Krzysztof suggested - check your previous project (if it is still avialable) by going to the project, use the Admin menu (top right of the browser page, next to your name) and select "Manage this Project Area".  Check the Overview secton and scroll down till you see what is in the Associations section against Uses - Requirements.

anthony


permanent link
Krzysztof Kaźmierczyk (7.5k480103) | answered May 23 '13, 5:21 a.m.
Hello Gaetano,
To see what requirements are used you must navigate to admin panel for your project area and in Overview tab check in Association section what uses Requirements. Then you will find out what is using these requirements.

permanent link
Anthony Kesterton (7.5k9180136) | answered May 23 '13, 10:26 a.m.
JAZZ DEVELOPER
Hi

I am running 4.0.2 - so may be seeing slightly different behaviour.  In my setup, I need to have another tool linked in to handle requirements with RQM.  You used to be able to have requirements in RQM directly (without any other requirements tool connected) - but this does not appear to be the case any longer.

As Krzysztof suggested - check your previous project (if it is still avialable) by going to the project, use the Admin menu (top right of the browser page, next to your name) and select "Manage this Project Area".  Check the Overview secton and scroll down till you see what is in the Associations section against Uses - Requirements.

anthony

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.