Version: unspecified (using Devel) OS: All A copy and paste of elements in the activity diagram creates a new widget but no new xmi element. Reproducible: Always Steps to Reproduce: 1. Create a new activity diagram 2. Add an activity 3. copy/paste the activity into the same diagram 4. connect both activities with an activity transistion 5. save the file 6. load the file Actual Results: The transistion has both ends connected to the first activity. Expected Results: The transistion should have one end connected to the first and the other end to the second activity. Inspecting the xmi file shows that both activities have the same XMIid, which is wrong. I set the severity to major because umbrello users expects, at least for the activity diagram, that the copy and paste operation create an independent element, not a hidden link to the original object. In the class diagram for example the user sees clearly that a copy and paste operation creates a link, because a name change of the pasted class updates also the name of the element from which it has been copied. The state diagram, which is similar to the activity diagram, does not have this issue.
The use case diagram has a similar problem. Copy/pasted elements do have the same xmiid as the element from which they has been copied from, but umbrello forbids connecting the origin and the copied element because of the same id.
> The state diagram, which is similar to the activity diagram, does not have this issue. There are still cases which affects the state diagram, changed the title of this bug.
Bug https://bugs.kde.org/show_bug.cgi?id=107358 related to this issue.
SVN commit 1273895 by habacker: Fixed copy & pasting of elements in activity and state diagrams. M +6 -1 umlclipboard.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1273895
Adding a similar patch to fix the use case diagram issue do not fix the issue - need to analyse more.
The difference to state or activity diagram elements is that use case diagram elements have a uml object connected to, which is displayed in the list view. A copy and paste of such elements refers to the same uml object. To copy a use case element there is currently only the duplicate function in the context menu available, which is very unflexible and inconsistant. One cannot duplicate connections for example. The question is for what purpose this difference is good or required ? It provides a non uniq user interface. This issue has been already raised in https://bugs.kde.org/show_bug.cgi?id=107358, so a replacement of the duplicate function with copy&paste seem to make real sense and more natural.
Use case diagrams uses element linking on copy/paste by current design. A different implementation of this is handled at bug 107358.
set version-fixed-in from 4.8.0 changelog