Created attachment 132745 [details]
Paste transpose of filtered data
1. Assume there is a table of data with auto-filter turned ON.
2. The table is then filtered based on a specific key.
3. The filtered table is copied.
4.a. Clipboard is pasted (into same or another ODS file) with only value and transpose option UNCHECKED.
4.b. Clipboard is pasted (into same of another ODS file) with only value and transpose option CHECKED.
Both steps 4.a and 4.b should result in the filtered data only getting pasted.
1. At step 4.a the filtered data only is pasted (as expected).
2. At step 4.b the entire data is pasted (while transposing it of course)!
*** This bug has been marked as a duplicate of bug 92125 ***
Bug 92125 is a duplicate of Bug 45958 and they are about unfiltered columns.
But that is not what's reported here with transpose so I'll set this one to New.
I'll set to minor because result can be reached with 2 steps, first paste then transpose.
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Version: 126.96.36.199 (x64)
Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
CPU threads: 4; OS: Windows 6.3; UI render: default;
Locale: en-US (en_US); Calc: group threaded
Build ID: 00(Build:2)
CPU threads: 4; OS: Linux 5.3; UI render: GL; VCL: kf5
Locale: de-CH (en_US.UTF-8); UI: de-DE
*** Bug 140979 has been marked as a duplicate of this bug. ***
The bug is open/known since 2017, ... are there any plans to resolve it in the foreseeable future?
> The bug is open/known since 2017, ... are there any plans to resolve it in the foreseeable future?
Yeah, I'm working on it. Until now, I've debugged the code and I have an idea how to fix it.
Actually, it seems to me this case was never implemented. It is just missing.
But it is complicated code and I have to be careful not to break anything else.
Disclaimer: I'm an ordinary LibreOffice user. (I've already spent to about two days on it. I expect two more days are necessary.)
The proof of concept was successful. It is fixed in one case. I'm working now on all the other cases and write unit tests.
The main implementation is done. I've implemented it in a test-driven approach (first write the test, then the implementation).
There are more cases to handle than expected. The following cases are working:
* Different cell types: numbers, strings, formulas, rich text, empty cell
* Filtered transposed cells are selected
* Formula references to rows before and after filtered row
* Double reference (e.g. A1:A3)
* Relative and absolute formula references
* Reference to filtered row (#REF!)
* Formatting patterns (e.g. cell backgrounds and borders)
Next I'll test manually and polish the code. Afterwards, I'll submit the code.
I've submitted a patch to gerrit: https://gerrit.libreoffice.org/c/core/+/114450
Waiting for review
Estimated, I've invested about 2-3 work weeks of my personal time for fixing and testing filtering/transposing pasting issues.
scito committed a patch related to this issue.
It has been pushed to "master":
tdf#107348 tdf#45958 tdf#141215 tdf#141683 fix filtered/transpose paste
It will be available in 7.2.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
I'm impressed by your unit tests in yor code, scito. I will try to verify this bug in the next 2 days.
(In reply to BogdanB from comment #13)
> I'm impressed by your unit tests in yor code, scito.
I've tried to catch all cases.
> I will try to verify this bug in the next 2 days.
Currently, I'm working on cut transpose issues (bug 68976, bug 142065, bug 71058). I'll reuse the unit test setup and slightly enhance it for cut. It is really helpful. Probably next weekend, I'll submit a patch for the cut issues.
Verified. Working well in
Version: 188.8.131.52.alpha0+ / LibreOffice Community
Build ID: 1a99b4e44190e182d56a04678850d62635d74c65
CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US