No StereoTypeEx can be reported for external req

[Marco Schramp]

Steps to reproduce:
- Create a report tempate
- Add the section Package/Element/External Requirements
- Pop up list of possible fields only shows StereoType, but no StereoTypeEx  


Please add this field in your next build.

[Andrew Warner]

Hear, hear!
I've been busting my head trying to figure out why my stereotyped items aren't returning from a simple search. It's because they're not the primary stereotype...except when they are?!? And, that's entirely dependent upon what order you apply the stereotypes.

I have yet to grasp the need for some stereotypes being more equal than others but please can we have a simple way to determine if an element has a stereotype? When I ask the question "is this element of the stereotype «blah»?" a simple yes or no will suffice.

It's also not clear to me whether or not I have to remove the stereotype attribute AND the stereotypeex attribute from element or not when I'm operating through the API.

It's too late on a Friday arvo for this. Time to go home.

Cheers,
Andrew.

[Paolo F Cantoni]

Andrew,

If you want to end up with NO stereotype then I think you have to remove both.  Certainly, through the UI you have to manage both the primary stereotype and the auxiliaries.

I support your request for the simple query.   Submit a formal Feature Request, let us know its exact tittle and we can formally support it by submitting references.

Given, as you say (and many of us previously confirmed) the order is arbitrary, perhaps the Feature Request (or another one) could add a sequencing feature.

HTH,
Paolo