Bug 133096 - editing: ui: calc: sort: 'copy output to' questionable workflow, changes unexpectedly references to target area
Summary: editing: ui: calc: sort: 'copy output to' questionable workflow, changes unex...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.8.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Sorting
  Show dependency treegraph
 
Reported: 2020-05-16 16:51 UTC by b.
Modified: 2024-09-05 03:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
file to illustrate, see descr. in OP (12.47 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-05-16 16:52 UTC, b.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description b. 2020-05-16 16:51:10 UTC
Description:
it looks as if with the sequence <data - sort - option - copy output to> not! the sorted output is copied into the target area - as one would expect from the naming of the option, but instead the unsorted! data is transferred into the target area and sorted there, what - unfortunately - (with the normally useful option <tols - options - libreoffice calc - general - update references when sorting range of cells>) messes 'external' references to the target area. 

i have understood that the option changes references to the source area (even if some other users find it difficult to accept), but changing references to something other than the source area irritates ... at least normal users ... 

since the intended result can be achieved by disabling the option 'update references', this bug is rather minor, but if someone works in this area it would be nice to change it, 

or the sort option should be named as: 'copy values to <target area> and sort there', 'copy output' as it's named now says 'first action - sort - producing output, then copy output to target area', thus the user expects no changes in the references to this area.

Steps to Reproduce:
1. load sheet from next comment, 
2. follow manual procedure in rows 1-10, see sorted output in H4:H8, 
3. check <tools - options - libreoffice calc - general - update references when sorting ranges of cells>, 
4. copy formulas from H4:H8 to H14:H18, 
5. range B14:B18 - data - sort - colB - ascending - option - copy output to - F14:F18, 
6. see references in H14:H18 messed up and thus result unsorted, 
7. un!check <tools - options - libreoffice calc - general - update references when sorting ranges of cells>, 
8. no need to copy formulas from H4:H8 to H24:H28, not messed up, 
9. range B24:B28 - data - sort - colB - ascending - option - copy output to - F24:F28, 
10. see references in H24:H28 unchanged and thus sorted results, 


Actual Results:
changed references, 'updated', results 'unsoirted', 

Expected Results:
copy sorted! output! to target area, and thus don't mess downstream work ... 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
6.2.8.2 as well as 7.0.0.0.a1+,
Comment 1 b. 2020-05-16 16:52:52 UTC
Created attachment 160905 [details]
file to illustrate, see descr. in OP
Comment 2 Buovjaga 2020-09-04 13:48:38 UTC
Reproduced.

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: 6b2eff7d69c6e14d89dd33eaa58c01d82c541266
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 4 September 2020
Comment 3 QA Administrators 2022-09-05 03:36:43 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2024-09-05 03:17:08 UTC
Dear b.,

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

MassPing-UntouchedBug