Bug 454739 - [Use Case diagram] Stereotype visibility depends on creation method
Summary: [Use Case diagram] Stereotype visibility depends on creation method
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.1.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 455311
Blocks: 457024
  Show dependency tree
 
Reported: 2014-12-10 09:59 EST by Johan Van Noten CLA
Modified: 2015-06-09 08:19 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Van Noten CLA 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 CLA 2015-06-09 08:19:14 EDT 
Fixed in 1.1 Mars release.