Can't Delete Custom Artifact Types in Rational Requirements Composer
![]() I have an issue with deleting custom Attributes and Artifact Types in RRC. When I set the project up, I created a custom attribute called "Capability". The team decided that they wanted a different format for that attribute (enum vs. string), so I deleted the one I created and created it with the new type. The old version of the attribute remained visible, but not accessible. If I tried to use it, my computer would just keep trying to load it and eventually time out. I figured it didn't hurt anything since it was a back end sort of error and left it. Now, however, we are having the same problem with the Artifact Types. When we turned the project over to the team, one of the members was given project admin rights to create new Artifact Types. They did the same thing I had done and deleted old types and created new ones. THe old deleted ones are still in the list when they go to create a new Artifact Type so they are presented with a drop down that has multiple SRS, SSS, etc and they have to hope they are lucky and pick the right one. Now I have to clean it up and I am concerned about two things. 1. Why can't I completely delete a custom attribute if there are no records with that data type in them? (which is the situation with the "capability" attribute since I deleted that prior to migrating or creating any records.) 2. Would there be any way to determine if an individual requirement is assigned to an artifact type that is "deleted"? In other words, if they created the requirement as an SRS (version 1) and then deleted SRS (version 1) and created an artifact type (version 2) - is there a way to tell in the requirement? Sorry it is so confusing. Right now I only see the option of creating a brand new project area and starting from scratch, but that affects the entire program (meaning RTC and RQM which have links to RRC) and I'm trying to avoid that.
|
One answer
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.