Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 454739

Summary:	[Use Case diagram] Stereotype visibility depends on creation method
Product:	[Modeling] Papyrus	Reporter:	Johan Van Noten <johan>
Component:	Diagram	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	Celine.janssens, papyrus-bugs
Version:	1.0.1
Target Milestone:	1.1.0
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	455311
Bug Blocks:	457024

Description Johan Van Noten

2014-12-10 09:59:36 EST

Version: v1.0.1 nightly

Good scenario:
* Create package
* Create use case diagram
* Drag use case from palette
* Leave the use case selected
* Go to properties, profile tab
* Apply a stereotype (I have a own dynamic profile applied to my model)
* Result: stereotype is visible <<myStereotype>> on the use case notation and on the model explorer.

Bad scenario:
* Drag use case from the palette
* Select the newly created use case in the model explorer
* Go to properties, profile tab
* Apply a stereotype
--> Stereotype does not become visible on the diagram.

Tried:
* The filter "Show/Hide compartments" seems set identically in good/bad case.
* Dragging an existing stereotyped use case into a use case diagram also doesn't show the stereotype.

Comment 1 Celine Janssens

2015-06-09 08:19:14 EDT

Fixed in 1.1 Mars release.