Bug 327887 - Classes copied and paste in new instance do not have package name
Summary: Classes copied and paste in new instance do not have package name
Status: RESOLVED WORKSFORME
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: 2.31.3 (KDE releases 20.04.3)
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-21 09:09 UTC by Ralf Habacker
Modified: 2021-03-11 22:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
test xmi file (1.15 MB, text/x-xmi)
2013-11-21 09:09 UTC, Ralf Habacker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2013-11-21 09:09:16 UTC
Copy and paste of class diagram widgets assigned to a package into a new umbrello instance are not assigned to the related package name

Reproducible: Always

Steps to Reproduce:
1. open appended file
2. select diagram "console"
3. Select all widgets and copy them
4. open new umbrello instance and paste widgets into
Actual Results:  
package names are not displayed

Expected Results:  
package should be pasted too
Comment 1 Ralf Habacker 2013-11-21 09:09:51 UTC
Created attachment 83674 [details]
test xmi file
Comment 2 Justin Zobel 2021-03-09 07:00:29 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Ralf Habacker 2021-03-11 22:33:28 UTC
With version 2.31.3 the selected widget could not be imported into a different umbrello instance. Instead an error dialog is shown mentioning that the import may have a wrong type.
Comment 4 Ralf Habacker 2021-03-11 22:44:33 UTC
(In reply to Ralf Habacker from comment #3)
> With version 2.31.3 the selected widget could not be imported into a
> different umbrello instance. Instead an error dialog is shown mentioning
> that the import may have a wrong type.
This issue was caused by an installation problem. 

I retested with a fresh build of the stable branch (2.31.3) and was not able to reproduce the issue reported by this bug.