Bug 502351

Summary:	[Model Explorer] [FACET] Papyrus-RT Protocol menu item is not expanded when create a protocol message from the new child menu
Product:	[Modeling] Papyrus-rt	Reporter:	smaoui asma <asma.smaoui>
Component:	tool	Assignee:	Project Inbox <papyrusrt-inbox>
Status:	UNCONFIRMED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	charles, peter.cigehn, sredding
Version:	unspecified	Keywords:	Documentation, readme
Target Milestone:	Future
Hardware:	PC
OS:	Windows 7
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=480403
Whiteboard:	depends_on_papyrus
Bug Depends on:	496486
Bug Blocks:

Description smaoui asma

2016-09-28 00:59:59 EDT

The aim of this bug is to track Bug 496486. Whenever this bug is fixed, the workaround proposed for Papyrus RT in Bug 480403 should be removed.

The main issue is the fact that model explorer view did not well interface with facet: newly created child item is not automatically selected (container item menu is not expanded) if the parent semantic element is not the real container of the child sementic element 

Example in Papyrus RT that illustrates this bug: when creating a protocol message, the Protocol menu item is not expanded and the newly created protocol message is not automatically selected

Comment 1 Peter Cigehn

2016-09-28 03:32:21 EDT

Could we give this Bugzilla some other name, more indicating what should be done in Papyrus-RT, instead of repeating the same name as the Papyrus Bugzilla it tracks? The notification mails from Bugzilla becomes quite confusing with two different Bugzillas with exactly the same name.

Comment 2 Charles Rivet

2016-10-31 14:32:57 EDT

Is this still an issue?

Comment 3 smaoui asma

2016-10-31 17:14:24 EDT

(In reply to Charles Rivet from comment #2)
> Is this still an issue?

This is only a track of a Papyrus bug : Bug 496486. In Papyrus RT, I already proposed a workaround in Bug 480403 (0.8.0 bug).

So this will still an issue until the Papyrus Bug is resolved.

Comment 4 Charles Rivet

2016-11-16 14:05:54 EST

Assigned to Rémi to reassign/close when Papyrus bug is closed.

Comment 5 Peter Cigehn

2017-03-06 12:33:37 EST

I guess that since Bug 496486, which this bug depends on, will not make its way into Neon.3, that we re-plan this one for 1.0 (or Future).

Comment 6 Remi Schnekenburger

2017-03-14 12:26:45 EDT

I agree, we should postpone it to a later release, this is only a tracker for a Papyrus generic solution. The feature is working in our case thanks to a workaround, fixing it now or later will not affect end users.

Comment 7 Remi Schnekenburger

2017-03-14 12:27:43 EDT

(And removing me from assignee, as I no longer assign tasks to CEA employees).

Comment 8 Simon Redding

2017-04-25 12:28:09 EDT

Bug 496486 will not be fixed for R1 so this bug needs to go to future.