Bug 144048 - Calc: Define Range doesn't set selected range
Summary: Calc: Define Range doesn't set selected range
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoFilter Calc-DataRange
  Show dependency treegraph
 
Reported: 2021-08-24 09:21 UTC by Timur
Modified: 2025-04-23 03:10 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
screencast (912.83 KB, video/mp4)
2021-08-25 07:38 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2021-08-24 09:21:33 UTC
1. Open ODS attachment 144970 [details] from bug 119949
2. Remove existing Autofilter (press Autofilter twice).
3. Mark the area to which the filter should be applied: A1-A6 or A1-A8. 
4. Set: Menu Data > Define Range. Enter Name, Add, OK.
5. With the area marked, enable Autofilter by menu Data > Autofilter.

Experienced: Autofilter also includes rows "this, stuff, shouldn’t be displayed".
Expected: Autofilter has range as defined. 

These are Regina's steps, which work in general, but somehow not in this case.
Comment 1 Timur 2021-08-24 09:35:06 UTC
Better to test with A1-A8.
In OO 3.3 range would not include A9-A11 (OK), but also not A7-A8 (NOK).
Bug as in Description already in LO 3.5 up to 7.3+.
Comment 2 m_a_riosv 2021-08-24 20:47:45 UTC
Maybe I didn't follow fine the steps, but no issue for me.
Version: 7.2.0.4 (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL
Comment 3 Timur 2021-08-25 07:38:30 UTC
Created attachment 174528 [details]
screencast
Comment 4 m_a_riosv 2021-08-25 09:48:55 UTC
Ok, I see now, but I'm not sure if it isn't done on purpose.
Comment 5 QA Administrators 2025-04-23 03:10:22 UTC
Dear Timur,

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