Profile deleted

[Darlene]

Just upgraded from version 9 to version 10.  A Profile exists to extend a requirement object to have custom tag values.  If I change the Requirement Type field for a Requirement based on the custom tag values associated with a Requirement object are being deleted.

[qwerty]

If you change the Type that will change the Stereotype of the Req. element. It's a bit brain damaged, but that's EA. You need to define individual (Stereo)types for requirements to fit into your MDG.

I had a strange effect where I had a "System" requirement and EA automagically changed that to "system" (or maybe it was vice versa with the capitals). But simply the requirement was not what was expected and did not belong to the MDG.

q.

[Darlene]

In my original posting, I have an editing issue with the 2nd sentence.  What I was attemting to say is ...
If I change the Requirement Type field for a Requirement object that is based on a Profile containing custom tag values, the custom tag values are deleted when the change is saved.

[qwerty]

Actually the cause is the same. You change the stereotype and with this you cut the  connection to the MDG. What makes me wonder is that this process makes the tags disappear. I just made a test with a simple element from a private MDG and after changing the stereotype this removed the tags. Changing the stereotype back again revealed them once again. Not sure where this is intentional or a bug.

q.

[edit] Obviously the tags are physically removed and later re-applied as their contents gets lost.

This behavior was obviously introduced with V10. In V9.3 the tags are not removed. I guess you have discovered a bug and you should report it via the link bottom right.

[Darlene]

qwerty, Thanks for your help.