Bug 132430 - Draw: Copy & paste a grouped object doesn't preserve the layer of single components
Summary: Draw: Copy & paste a grouped object doesn't preserve the layer of single comp...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Layers
  Show dependency treegraph
Reported: 2020-04-26 10:52 UTC by Giorgio Croci Candiani
Modified: 2024-05-06 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Example document showing bug (74.70 KB, application/vnd.oasis.opendocument.graphics)
2020-05-12 08:35 UTC, Giorgio Croci Candiani

Note You need to log in before you can comment on or make changes to this bug.
Description Giorgio Croci Candiani 2020-04-26 10:52:07 UTC
When copying a grouped object containing parts on different layers, pasting puts all parts on the target layer rather than preserving the original ones

Steps to Reproduce:
1.Draw several object on different layers.
2.Group these objects (Ctrl-Shift-G)
3.Select the grouped object and copy it with Ctrl-C
4.Paste the obj with Ctrl-V to any layer "X"
5.Ungroup the obj group (Ctrl-Alt-Shift-G)

Actual Results:
All the copied sub-objects are on layer "X"

Expected Results:
All the copied sub-objects should have retained their original layer

Reproducible: Always

User Profile Reset: No

Additional Info:
Versione: (x64)
Build ID: dd0751754f11728f69b42ee2af66670068624673
Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: GL; VCL: win; 
Versione locale: it-IT (it_IT); Lingua interfaccia: it-IT
Calc: threaded
Comment 1 Xisco Faulí 2020-05-11 07:53:26 UTC Comment hidden (obsolete)
Comment 2 Giorgio Croci Candiani 2020-05-12 08:35:03 UTC
Created attachment 160714 [details]
Example document showing bug
Comment 3 Timur 2020-07-07 14:28:23 UTC
Looks as reported in OO 3.3 and master 7.1+.
Comment 4 Giorgio Croci Candiani 2022-05-06 08:16:17 UTC
Two years and the bug is still marked as "New", despite being a pretty basic flaw.  Not impressing at all.
Comment 5 QA Administrators 2024-05-06 03:15:03 UTC
Dear Giorgio Croci Candiani,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team