It's all about the answers!

Ask a question

RRC Artifact change the type when they are linked


Sylvain LEQUEUX (2132728) | asked Mar 14 '11, 12:07 p.m.
Hi,

We are currently having a bug in our installation and some help would be apretiated :)

Here is our configuration :
- RTC 3, RRC 2 and RQM 2 on separate Tomcat servers on Windows Server 2003
- One project on each server all linked together (for RTC to RRC, it's "change management (implementation)" association type).

Here is the test case which fails :
- Create a use case in RRC (let's name it UC1)
- Create a story in RTC (let's name it Story 1)
- From RTC Web UI (I haven't test the eclipse based client way yet), create a link "implements" from Story1 to UC1.
- Note that at this time, the UC1 is a UC.
- Save the change to create the link.
- The UC icon in the link list (RTC Web UI) has changed and is not the UC icon anymore.
- Back in RRC (eclipse based client), try to refresh (or simply open) the artifact. I get the error message :

CRRRC2220E Impossible d'ouvrir le rfrentiel "<ref>"
(https://<host>:9444/rdm/).
cause : com.ibm.rdm.ba.usecase.impl.UseCaseImpl incompatible with
com.ibm.rdm.requirement.Requirement

(sorry for the message which is not in english but I have a french client).

The UC has turned into a requirement and can't be opened anymore.
When creating the link from the use case in RRC to the story in RTC, the UC doesn't change.

Does anyone has any idea about where this bug can come from ?

Thanks.
Sylvain

3 answers



permanent link
Robin Bater (3.4k47) | answered Mar 23 '11, 10:26 a.m.
JAZZ DEVELOPER
Hi,

We are currently having a bug in our installation and some help would be apretiated :)

Here is our configuration :
- RTC 3, RRC 2 and RQM 2 on separate Tomcat servers on Windows Server 2003
- One project on each server all linked together (for RTC to RRC, it's "change management (implementation)" association type).

Here is the test case which fails :
- Create a use case in RRC (let's name it UC1)
- Create a story in RTC (let's name it Story 1)
- From RTC Web UI (I haven't test the eclipse based client way yet), create a link "implements" from Story1 to UC1.
- Note that at this time, the UC1 is a UC.
- Save the change to create the link.
- The UC icon in the link list (RTC Web UI) has changed and is not the UC icon anymore.
- Back in RRC (eclipse based client), try to refresh (or simply open) the artifact. I get the error message :

CRRRC2220E Impossible d'ouvrir le rfrentiel "<ref>"
(https://<host>:9444/rdm/).
cause : com.ibm.rdm.ba.usecase.impl.UseCaseImpl incompatible with
com.ibm.rdm.requirement.Requirement

(sorry for the message which is not in english but I have a french client).

The UC has turned into a requirement and can't be opened anymore.
When creating the link from the use case in RRC to the story in RTC, the UC doesn't change.

Does anyone has any idea about where this bug can come from ?

Thanks.
Sylvain

Sorry I don't have any ideas. Have you raised a defect work item?

permanent link
Alexander Schinko (35511812) | answered May 31 '11, 10:36 a.m.
Seems to be the same problem here (with french and english client)! Any solutions?

Hi,

We are currently having a bug in our installation and some help would be apretiated :)

Here is our configuration :
- RTC 3, RRC 2 and RQM 2 on separate Tomcat servers on Windows Server 2003
- One project on each server all linked together (for RTC to RRC, it's "change management (implementation)" association type).

Here is the test case which fails :
- Create a use case in RRC (let's name it UC1)
- Create a story in RTC (let's name it Story 1)
- From RTC Web UI (I haven't test the eclipse based client way yet), create a link "implements" from Story1 to UC1.
- Note that at this time, the UC1 is a UC.
- Save the change to create the link.
- The UC icon in the link list (RTC Web UI) has changed and is not the UC icon anymore.
- Back in RRC (eclipse based client), try to refresh (or simply open) the artifact. I get the error message :

CRRRC2220E Impossible d'ouvrir le rfrentiel "<ref>"
(https://<host>:9444/rdm/).
cause : com.ibm.rdm.ba.usecase.impl.UseCaseImpl incompatible with
com.ibm.rdm.requirement.Requirement

(sorry for the message which is not in english but I have a french client).

The UC has turned into a requirement and can't be opened anymore.
When creating the link from the use case in RRC to the story in RTC, the UC doesn't change.

Does anyone has any idea about where this bug can come from ?

Thanks.
Sylvain

Sorry I don't have any ideas. Have you raised a defect work item?

permanent link
Sylvain LEQUEUX (2132728) | answered May 31 '11, 11:19 a.m.
Hello,

This issue has been corrected in 2.0.0.4. Since we installed this version, we don't have this behaviour anymore.

Regards,
Sylvain

Seems to be the same problem here (with french and english client)! Any solutions?

Hi,

We are currently having a bug in our installation and some help would be apretiated :)

Here is our configuration :
- RTC 3, RRC 2 and RQM 2 on separate Tomcat servers on Windows Server 2003
- One project on each server all linked together (for RTC to RRC, it's "change management (implementation)" association type).

Here is the test case which fails :
- Create a use case in RRC (let's name it UC1)
- Create a story in RTC (let's name it Story 1)
- From RTC Web UI (I haven't test the eclipse based client way yet), create a link "implements" from Story1 to UC1.
- Note that at this time, the UC1 is a UC.
- Save the change to create the link.
- The UC icon in the link list (RTC Web UI) has changed and is not the UC icon anymore.
- Back in RRC (eclipse based client), try to refresh (or simply open) the artifact. I get the error message :

CRRRC2220E Impossible d'ouvrir le rfrentiel "<ref>"
(https://<host>:9444/rdm/).
cause : com.ibm.rdm.ba.usecase.impl.UseCaseImpl incompatible with
com.ibm.rdm.requirement.Requirement

(sorry for the message which is not in english but I have a french client).

The UC has turned into a requirement and can't be opened anymore.
When creating the link from the use case in RRC to the story in RTC, the UC doesn't change.

Does anyone has any idea about where this bug can come from ?

Thanks.
Sylvain

Sorry I don't have any ideas. Have you raised a defect work item?

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.